Interface display method and electronic equipment

Abstract

The invention provides an interface display method and electronic equipment, and relates to the technical field of terminals. The electronic equipment runs a table setting function in a doze state, and a first table setting interface is displayed. In the doze state, the AP of the electronic equipment is in an awakening state, the frame rate is the first frame rate, and the display brightness is the first brightness. Afterwards, under the condition that the time in the doze state reaches the first time, if the trigger operation of the user on the electronic equipment is not received within the first time, it is indicated that the user possibly does not have the requirement for using the table setting function at present, the electronic equipment can be switched to the dozespen state, and a second table setting interface is displayed. In the dozespen state, the AP of the electronic equipment is in the dormant state, the frame rate is the second frame rate, the display brightness is the second brightness, the second frame rate is smaller than the first frame rate, and the second brightness is smaller than the first brightness, so that the power consumption is reduced, and the use experience of a user is ensured.

Description

Technical Field

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

[0002] Currently, some electronic devices offer a smart display function (or display feature), allowing them to show a clock or other display interface. However, when the device is not charging, continuously displaying this display interface leads to higher power consumption, impacting battery life and resulting in a poor user experience. Summary of the Invention

[0003] This application provides an interface display method and an electronic device to reduce the power consumption of the electronic device, thereby ensuring the battery life of the electronic device and improving the user experience.

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

[0005] Firstly, a method for displaying an interface is provided, applied to an electronic device. When the electronic device is in a first state, it displays a first interface, which is the interface of a tabletop application. This first state indicates that the electronic device is in at least one of the following states: the frame rate of the electronic device's display is a first frame rate, the application processor (AP) of the electronic device is in a wake-up state, and the display brightness of the electronic device is a first brightness. After a first period of time, if no trigger operation is received on the electronic device within that first period, the electronic device can switch to a second state and display a second interface. This second interface is also the interface of the tabletop application; the second state indicates that the electronic device is in at least one of the following states: the frame rate of the display is a second frame rate, the AP is in a sleep state, and the display brightness of the electronic device is a second brightness. The second frame rate is lower than the first frame rate, and the second brightness is lower than the first brightness.

[0006] In this application, in the first state, the AP is in a wake-up state with high display brightness and a high frame rate, while in the second state, the AP is in a sleep state with low display brightness and a low frame rate. Therefore, compared to the first state, the power consumption in the second state is lower. The electronic device displays the interface of the table setting application in the first state. After a certain period of time, if no user trigger operation is received within that period, it indicates that the user is unlikely to be using the table setting application at that time. The electronic device can then switch to the lower-power second state and continue to display the interface of the table setting application in the second state, thereby reducing the power consumption of the electronic device and ensuring its battery life. Furthermore, after the first period of time, the electronic device does not directly exit the table setting application, which avoids the situation where the user wants to use the table setting application but cannot use it immediately, making it convenient for the user and improving the user experience.

[0007] In one possible design, after displaying the second interface, the electronic device receives a user's trigger operation on its display screen. In response to this trigger operation, the electronic device switches back to the first state, continuing to display the table setting application interface, i.e., the third interface. Therefore, upon receiving a user's trigger operation, indicating that the user wants to use the table setting application, the electronic device can switch to the higher-power first state to continue running the table setting interface, facilitating user operation.

[0008] In one possible design, the third interface includes a first card, and the second interface includes a second card. The first and second cards are of the same type, and this type includes at least one or more of the following: clock, weather, calendar, signature, and photo album. Based on this, when the electronic device switches states, the second interface switches to display the third interface. Since the second and third interfaces include cards of the same type, meaning the types of content displayed are the same, this avoids user confusion about why the interface type changes.

[0009] In one possible design approach, the third interface differs from the second interface in that it features animation effects, while the second interface remains static. Based on this, in the high-power first state, it indicates a higher likelihood of the user using a desktop application. Therefore, the electronic device can display an interface with animation effects to enhance its visual appeal and engagement, thereby improving the display effect and user experience.

[0010] In one possible design, when the second state indicates that the AP is in a sleep state, the electronic device can control the AP to enter a wake-up state every second time interval while displaying the second interface. Afterwards, the electronic device can update the second interface through the AP. Based on this, during the second state, the electronic device can periodically wake up the AP to update the displayed interface, avoiding screen burn-in and ghosting issues.

[0011] In one possible design, during the display of the second interface, the electronic device periodically wakes up the AP, and after a third period of time, controls the AP to enter a sleep state, or controls the AP to re-enter a sleep state after the second interface is updated, thereby reducing power consumption.

[0012] In one possible design, updating the second interface includes: the electronic device updating the position of objects in the second interface. Alternatively, the electronic device updates a first image in the second interface to a second image, wherein the first and second images correspond to cards of the same type.

[0013] In one possible design, the aforementioned electronic device can display the first interface when a first preset condition is met. The first preset condition represents the condition for activating the tabletop application. The first preset condition includes the electronic device being in a first device state and the electronic device meeting at least one of the following conditions: the electronic device has been in a static state for more than four hours, the electronic device is in a black screen state, the electronic device is in an AOD state, and the electronic device is in a screen-on-lock state. The first device state is either landscape mode or hover mode.

[0014] Based on this, if the electronic device meets the first preset condition, it indicates that the user may want to use the table setting application. In this case, the electronic device can first display the interface of the table setting application in the first state to ensure user experience.

[0015] In one possible design, under the condition of satisfying a first preset condition, namely when starting the tabletop application, the electronic device can also set the display driver pulse to a first pulse value, which is less than the second pulse value of the display driver before starting the tabletop application. In this application, compared to other applications using the electronic device, the user does not continuously look at the interface when using the tabletop application. Therefore, the electronic device can reduce the pulse value of the display driver, thereby reducing power consumption while meeting the user's usage needs.

[0016] In one possible design approach, when switching from the first state to the second state, the process of the electronic device reducing the display brightness to the second brightness may include: the electronic device directly setting the brightness of the display screen to the second brightness, or adding a first layer to the second interface, and displaying the second interface of the electronic device with the first layer added, with the display brightness of the electronic device being the second brightness, thereby reducing the display brightness of the electronic device and reducing the power consumption of the electronic device.

[0017] In one possible design, the electronic device can periodically or in real-time acquire the current ambient light intensity. Then, the electronic device determines whether the current ambient light intensity meets a second preset condition. This second preset condition indicates the conditions that trigger the electronic device to adjust the brightness of the display screen. If the current ambient light intensity meets the second preset condition, and the electronic device is in a first state, it can adjust the brightness of the display screen based on the current ambient light intensity. If the electronic device is in a second state, it controls the AP to enter a wake-up state and adjust the brightness of the display screen based on the current ambient light intensity.

[0018] Based on this, electronic devices adjust the brightness of the display screen to match the current ambient light intensity, thereby improving the user experience.

[0019] In one possible design, the ambient light intensity when the electronic device displays the first interface is the same as the ambient light intensity when the electronic device displays the second interface. Based on this, when the electronic device switches from the first state to the second state, it will reduce the display brightness even if the ambient light intensity remains unchanged, in order to reduce power consumption.

[0020] In one possible design approach, the aforementioned electronic device can be in an uncharged state, whether in the first state or the second state, thereby reducing the limitations of its use in tabletop applications.

[0021] Secondly, this application provides an electronic device, the electronic device including a memory, a display screen and one or more processors; the memory, the display screen and the processor are coupled; the memory is used to store computer program code, the computer program code including computer instructions; the display screen is used to display an image generated by the processor; when the processor executes the computer instructions, the electronic device performs the method described above.

[0022] 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.

[0023] Fourthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method described above.

[0024] It is understood that the beneficial effects achieved by the electronic device described in the second aspect, the computer-readable storage medium described in the third aspect, and the computer program product described in the fourth aspect can be referred to in the beneficial effects of the first aspect and any possible implementation thereof, and will not be repeated here. Attached Figure Description

[0025] Figure 1A A schematic diagram of a tabletop interface provided in this application embodiment;

[0026] Figure 1B A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 2 ;

[0027] Figure 2 A schematic diagram illustrating a state transition provided in an embodiment of this application;

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

[0029] Figure 4 A structural block diagram of an electronic device provided in an embodiment of this application;

[0030] Figure 5 A flowchart illustrating an interface display method provided in an embodiment of this application;

[0031] Figure 6A A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 3 ;

[0032] Figure 6B A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 4 ;

[0033] Figure 7 A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 5 ;

[0034] Figure 8 A schematic diagram of a tabletop interface provided in this application embodiment is shown in Figure 6.

[0035] Figure 9 A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 7 ;

[0036] Figure 10 A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 8 ;

[0037] Figure 11 A schematic diagram of a tabletop interface provided in an embodiment of this application. Figure 9 ;

[0038] Figure 12 A flowchart illustrating an interface display method provided in this application embodiment. Figure 2 ;

[0039] Figure 13 A flowchart illustrating an interface display method provided in this application embodiment. Figure 3 . Detailed Implementation

[0040] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "exemplary" or "for example" are used in the embodiments of this application to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a specific manner. In the embodiments of this application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing 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. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In the embodiments of this application, "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 indicated technical features. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0041] The following will introduce some of the terms used in this application.

[0042] Foldable device: An electronic device equipped with a foldable screen (i.e., a foldable display). A foldable device can be unfolded into an unfolded state, folded into a folded state, or in a hovering state between the unfolded and folded states. In other words, the hovering state represents the state of the electronic device on the switching path between the folded and unfolded states.

[0043] Frame rate: also known as refresh rate, refers to the number of frames that refresh an image per unit time (e.g., 1 second). It can also be understood as the number of times the graphics processor in an electronic device refreshes the screen per second.

[0044] A "display application" refers to a standalone application used to display specific cards, such as clocks, electronic photo albums, calendars, weather, and personalized signatures (or signatures), in full screen when an electronic device is in a specific device state (e.g., landscape mode). The electronic device can function as a display stand. Optionally, in this application, "display application" can also be described as a display function or a standby application. It should be understood that a display application can also have other names, and this application is not limited to them.

[0045] In some embodiments, the electronic device provides a table-setting function. When the electronic device is placed horizontally and charging, after entering standby mode, the electronic device can display a table-setting interface (such as...). Figure 1A (As shown). However, when the electronic device is not charging, it cannot display the table setting interface, thus limiting the use of the table setting function.

[0046] Therefore, to reduce limitations on the use of the display screen function, electronic devices support an all-day display mode when not charging. When the electronic device is placed in landscape mode and enters standby mode, it can continuously display the display screen. Alternatively, the display screen can be shown for a period of time (e.g., 20 seconds) before the device stops displaying it. The display screen can be redisplayed when the user taps it. For example, a mobile phone might display... Figure 1B In the table setting interface shown in (a), after 20 seconds, the phone stops displaying the table setting interface and enters a black screen state (e.g., Figure 1B As shown in (b)). Then, when the user taps the phone's screen (as shown in [image]), Figure 1B When shown in (c), the electronic device responds to the user's click operation and displays as shown in (c). Figure 1B The tabletop interface shown in (d) is shown in the middle.

[0047] However, when electronic devices continuously display the clock facet interface, their power consumption is high, shortening their battery life. Alternatively, while electronic devices can reduce power consumption by stopping the display after a period of time, users still need to perform additional operations to use the clock facet function. For example, to check the time, users need to tap the screen before the clock facet interface appears, causing inconvenience.

[0048] Therefore, to address the aforementioned issues, this application defines two states for the screen placement function: a doze state (or first state) and a dozesuspend state (or second state). The doze state indicates that the electronic device is in at least one of the following states: the screen's frame rate is a first frame rate, the AP is awake, and the screen brightness is a first brightness. The dozesuspend state indicates that the electronic device is in at least one of the following states: the screen's frame rate is a second frame rate, the AP is asleep, and the screen brightness is a second brightness. The first frame rate is greater than the second frame rate, and the first brightness is greater than the second brightness. Compared to the doze state, the dozesuspend state has a lower screen frame rate, lower brightness, and the AP is asleep; therefore, the dozesuspend state requires less power.

[0049] The doze state and dozesuspend state can be switched between each other (e.g., Figure 2 (As shown). Electronic devices can switch from a high-power "doze" state to a low-power "dozesuspend" state based on user activity, instead of continuously running the screen-setting function in "doze." This reduces power consumption and minimizes the impact of the screen-setting function on battery life. Furthermore, even when running the screen-setting function in "dozesuspend," users can immediately access it when needed, meeting their requirements and avoiding situations where the screen is black and the user has to re-trigger the function, thus improving the user experience.

[0050] For example, the aforementioned electronic device may be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as wearable devices, personal digital assistants (PDAs), augmented reality (AR) / virtual reality (VR) devices, and other electronic devices with a display screen. This application embodiment does not impose any special limitations on the specific form of the electronic device. Additionally, optionally, the display screen of the electronic device may or may not be a foldable screen.

[0051] Figure 3 A schematic diagram of the structure of the electronic device 100 is shown.

[0052] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc.

[0053] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 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.

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

[0055] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of instruction fetching and execution.

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

[0057] In some embodiments, the aforementioned AP is primarily responsible for processing the business logic of the electronic device's application and system management tasks, including application display, user interaction, adjusting the display's pulses, adjusting the display's brightness, and receiving data sent by the electronic device's sensors.

[0058] The aforementioned GPU is primarily responsible for image rendering, such as drawing application interfaces and rendering captured images.

[0059] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0060] 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 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0061] While charging the battery 142, the charging management module 140 can also supply power to electronic devices through the power management module 141.

[0062] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0063] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

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

[0065] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0066] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0067] In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0068] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0069] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0070] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0071] The sensor module 180 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 (or ambient light intensity sensors), bone conduction sensors, etc.

[0072] Among them, the ambient light sensor is used to collect information on the current ambient light intensity of electronic devices.

[0073] Buttons 190 include a power button, volume buttons, etc. Motor 191 can generate vibration feedback. Indicator 192 can be an indicator light, used to indicate charging status, battery level changes, and also to indicate messages, missed calls, notifications, etc.

[0074] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1.

[0075] The software system of electronic device 100 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 exemplify the software structure of electronic device 100.

[0076] Figure 4 This is a structural block diagram of an electronic device 100 according to an embodiment of the present invention.

[0077] 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, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0078] The application layer can include a series of application packages.

[0079] like Figure 4 As shown, the application package may include applications (or simply applications) such as camera, gallery, calendar, call, map, standby, WLAN, Bluetooth, music, video, and SMS.

[0080] 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.

[0081] like Figure 4 As shown, the application framework layer may include a window manager, content provider, view system, brightness module, resource manager, notification manager, etc.

[0082] The brightness module is used to provide parameter information for layers (such as alpha layers) to standby apps. Optionally, this parameter information can be a value for transparency or opacity.

[0083] The window manager is used to manage window programs. The content provider is used to store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0084] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0085] The Android Runtime consists of core libraries and a virtual machine. The Android Runtime is responsible for the scheduling and management of the Android system.

[0086] 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.

[0087] The application layer and application framework layer run in a virtual machine. System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0088] The Surface Manager manages the display subsystem and provides fusion of 2D and 3D layers for multiple applications. The 3D graphics processing library implements 3D graphics drawing, image rendering, compositing, and layer processing. The 2D graphics engine is the drawing engine for 2D graphics.

[0089] The kernel layer is the layer between hardware and software. The kernel layer contains at least a display driver and sensor drivers. Optionally, the sensor drivers may include an ambient light sensor driver (or an ambient light intensity sensor driver).

[0090] In some embodiments, the software layer and the hardware layer can communicate, with the sensor driver acquiring data collected by the sensor and reporting the data upwards. For example, the ambient light sensor driver can acquire the current light intensity information collected by the ambient light sensor and send the current light intensity information to the AP. As another example, the display driver can drive the display screen to display a picture.

[0091] This application provides an interface display method. When an electronic device needs to run a screen-setting function, it can first enter a doze state to operate the screen-setting function. In the doze state, the electronic device's access point (AP) is awake, the display screen has a high frame rate and high brightness, and the device consumes a significant amount of power. If no touch event is received from the user within the doze state (time 1), it indicates that the user is not using the screen-setting function and may not currently have a need for it. The electronic device then switches from the doze state to the dozesuspend state to continue operating the screen-setting function. In the dozesuspend state, the electronic device's AP is in sleep mode, the display screen has a low frame rate and low brightness, and the device consumes less power. This reduces power consumption while ensuring the screen-setting function continues to operate. Therefore, when the user needs to use the screen-setting function, they can use it immediately without needing to perform any user actions, improving user convenience and satisfaction.

[0092] The following will use a mobile phone as an example to illustrate the switching process between the doze state and the dozesuspend state during the operation of the aforementioned tabletop function, which is to say, the implementation flow of the interface display method. Specifically, as follows... Figure 5 As shown, the implementation process is as follows:

[0093] S201. When the conditions for setting up the phone are met, the phone enters doze state. In doze state, the phone's AP is awake, the phone's display frame rate is 1, and the phone's display brightness is 1.

[0094] The table setting entry condition is used to trigger the mobile phone to launch the table setting application, that is, to run the table setting function and display the table setting interface. For example, the table setting entry condition (or the first preset condition) may include the device state of the electronic device being state 1 (or the first device state), and including at least one of the following conditions: the electronic device has been in a static state for more than time 2 (or the fourth time), is in a black screen (or screen off) state, is in an always on display (AOD) state, or is in a screen-on lock state.

[0095] The above state 1 refers to the landscape mode, or when the phone is a foldable device, the above state 1 refers to the hover mode.

[0096] For example, the frame rate 1 (or first frame rate) mentioned above represents a high frame rate, such as 60Hz or other frame rates, like 90Hz. The brightness 1 (or first brightness) mentioned above represents high brightness.

[0097] It should be noted that the above-described conditions for setting up a table are only an example. Other conditions may also be included, such as receiving a user's activation operation. This application does not impose any restrictions on the conditions for setting up a table.

[0098] S202, The mobile phone displays the tabletop interface corresponding to the doze state 1.

[0099] Here, the display interface 1 (or first interface) refers to the display interface shown on the phone in doze mode. For example, the types corresponding to the display interface may include clock, calendar, weather, signature, electronic photo album (or photo album), etc. Display interface 1 may include animation effects. Taking the clock type as an example, display interface 1 may include a clock, where the hour, minute, and second hands are moving, such as... Figure 6A The second hand on the display screen 1 shown points to the number 4. This second hand moves continuously over time, and after 5 seconds, it points to the number 5 (as shown). Figure 6B (As shown). Optionally, the display interface includes cards, and the type corresponding to the display interface indicates the type of cards included in the display interface. These cards can be simply understood as images included in the display interface.

[0100] In this embodiment, when the mobile phone meets the conditions for entering the display screen, it indicates that the mobile phone needs to run the display screen function, that is, it needs to enter the standby state. The mobile phone can then run the display screen function in a high-power doze state. Specifically, the mobile phone can keep the AP (Application Processor) awake and the display screen at a high frame rate, so that the GPU can continuously update the content displayed on the display screen, maintaining the smoothness of the animation effects, increasing the visual appeal and engagement of the display screen, and ultimately improving the user experience.

[0101] Alternatively, the phone may not run the table setting function if the conditions for entering the table setting are not met, and it does not need to be in doze or dozesuspend state.

[0102] It should be noted that any changes (i.e., updates) to the content on the display screen require the GPU to redraw, as mentioned above. Figure 6A The second hand moves from 4 to 5, and this movement requires GPU rendering. Therefore, during the doze state, the application program (AP) needs to remain awake so that the GPU can render the animation in the tabletop interface.

[0103] S203. If the display time of the above-mentioned display interface 1 reaches time 1, and no trigger operation on the display screen is received within time 1, the mobile phone switches from doze state to dozesuspend state and displays the display interface 2 corresponding to the dozesuspend state.

[0104] The aforementioned triggering operations may include at least click operations and / or swipe operations (such as swipe up, swipe down, swipe left, swipe right).

[0105] S204, The mobile phone performs AP sleep operation.

[0106] S205, The phone reduces the screen frame rate to frame rate 2.

[0107] Here, frame rate 2 (or the second frame rate) is less than frame rate 1. For example, frame rate 2 can be a small value such as 0 Hz or 0.1 Hz.

[0108] In this embodiment, since the AP of the mobile phone is in a dozesuspend state and does not perform drawing operations, the content displayed on the screen does not need to change. Therefore, the mobile phone can reduce the frame rate of the screen to reduce the power consumption of the mobile phone.

[0109] S206. The phone reduces the display brightness to brightness 2.

[0110] For example, in dozesuspend mode, the phone's AP is in sleep mode, the display frame rate is a lower frame rate 2, and the phone's display brightness is a lower brightness 2 (i.e., brightness 2 is less than the brightness 1 mentioned above). In addition, brightness 2 can also be described as a second brightness.

[0111] Here, "Standing Interface 2" refers to the screen displayed on the phone during dozesuspend mode. In dozesuspend mode, since the application processor (AP) is in sleep mode and the GPU cannot render, Standing Interface 2 may not include animation effects; the content displayed can be static. Taking a clock type as an example, Standing Interface 2 can include, for instance... Figure 7 The clock shown does not include a second hand.

[0112] In this embodiment of the application, if the mobile phone is in the doze state for time 1 (or the first time) and no user input is received to trigger the display screen during time 1, that is, no touch event is received, it indicates that the user may not currently have a need to use the screen-setting function. In order to reduce the power consumption of the mobile phone and facilitate the user's use of the screen-setting function, the mobile phone does not turn off the screen-setting function, but switches to the lower power consumption dozesuspend state and continues to run the screen-setting function in the dozesupend state.

[0113] Additionally, if a user touch event is received within time 1, the phone can remain in doze state and perform the corresponding operation in response to that touch event, without switching to dozesuspend state. Furthermore, the phone will restart its timer to record the time spent in doze state. For example, if time 1 is 20 seconds, and the phone receives a swipe-up input from the user after 15 seconds in doze state, the doze state time will be reset to zero, and the timer will restart.

[0114] It should be noted that the numbering of the above steps does not represent the order in which the steps are executed. For example, steps S204-S206 can be performed simultaneously or sequentially. This application does not impose any restrictions on the order in which the steps are executed. However, it is understandable that step S203 is executed before step S204. The phone needs to use the GPU to complete the rendering of the tabletop interface 2 before controlling the AP to enter sleep mode.

[0115] In some embodiments, the methods for adjusting the display brightness of a mobile phone may include layer adjustment, screen brightness adjustment, etc. The following sections will describe layer adjustment and screen brightness adjustment methods in detail.

[0116] In one implementation, the phone can add Layer 1 (or the first layer) to the display screen 2 to achieve a masking effect, darkening the phone's backlight and reducing the phone's display brightness to Brightness 2. Layer 1 can be a layer with adjustable transparency, such as an Alpha (α) layer as shown in the image. Specifically, the phone can add Layer 1 to the display screen 2 and set the transparency of Layer 1 to a value of 1 (or Transparency 1), where 1 is a number between 0 and 1.

[0117] The value 1 mentioned above can be a preset value. Alternatively, the value 1 can be a value randomly selected by the mobile phone.

[0118] Alternatively, the aforementioned value 1 could be determined by the phone based on the remaining battery power. For example, the phone could determine a value 1 corresponding to the remaining battery power, which could then be used to add layer 1. The lower the remaining battery power, the more power-efficient the phone needs to be, allowing it to adjust its backlight to a lower level and thus reduce the transparency. For instance, when the remaining battery power is 80%, the phone determines the value 1 corresponding to 80% to be 0.7; when the remaining battery power is 60%, the phone determines the value 1 corresponding to 60% to be 0.45.

[0119] It should be noted that the above method adjusts the phone's backlight by setting the transparency. Of course, the phone's backlight can also be adjusted by using the opacity, but the transparency and opacity settings are opposite. The higher the opacity, the lower the phone's backlight.

[0120] In addition, the addition of layer 1 can be performed by the phone's GPU. In other words, the addition of layer 1 is an operation performed by the phone's AP before entering sleep mode.

[0121] In another implementation, the phone can reduce its backlight by lowering the brightness of the display itself, thus reducing the overall brightness. For example, in doze mode, the phone's display brightness is 100 nits. When the phone switches from doze mode to dozesuspned mode, the display brightness is set to 50 nits. The 100 nits can be understood as brightness 1 above, and the 50 nits as brightness 2 above.

[0122] It is understandable that the adjustment of display brightness caused by switching between doze state and dozesuspend state is unrelated to the ambient light intensity. Even if the ambient light intensity is the same, the phone will still adjust the display brightness. For example, if the ambient light intensity is the same when the phone is in doze state and after the phone switches to dozesuspend state, the phone will still reduce the display brightness to brightness 2.

[0123] In some embodiments, the switching between the doze state and the dozesuspend state described above can occur when the phone is not charging, specifically, in the non-charging all-day display mode. When the phone is in non-charging all-day display mode, if the phone is not charging and no touch event is received after the time in the doze state reaches time 1, the phone can switch to the lower power consumption dozesuspend state.

[0124] Alternatively, when charging, the phone can remain in the doze state instead of switching from doze to dozesuspend to ensure a better user experience. Of course, the phone can also switch from doze to dozesuspend while charging to reduce power consumption.

[0125] It should be noted that the actions described above—reducing the phone's display brightness, putting the AP to sleep, and lowering the display's frame rate—when switching to dozesuspend state are merely exemplary operations performed by the phone to reduce power consumption. The phone may also perform only one or two of these operations. In other words, steps S204, S205, and S206 are optional, and the phone can execute one or more of these steps.

[0126] The preceding sections S203-S206 described the process of the phone switching from doze state to dozesuspend state. While the phone is running the table setting function in dozesuspend state, upon receiving a user input trigger, it indicates that the user currently needs to use the table setting function. To improve the user experience, the phone can switch back from dozesuspend state to doze state. The following section will continue to describe the process of the phone switching back from dozesuspend state to doze state.

[0127] S207. The mobile phone receives user click operations on the display screen.

[0128] S208. In response to the above click operation, the phone switches from dozesuspend state to doze state.

[0129] S209, The mobile phone performs an AP wake-up operation.

[0130] S210, the phone increases the display frame rate to frame rate 3.

[0131] Frame rate 3 is greater than frame rate 2. Furthermore, frame rate 3 may or may not be equal to frame rate 1; this application does not limit its application. Optionally, frame rate 3 may also be described as a first frame rate.

[0132] The specific implementation process of S210 can be referred to the relevant description of S205 above.

[0133] S211, The phone increases the display brightness to brightness 3.

[0134] In this context, brightness 3 is greater than brightness 2. Furthermore, brightness 3 may be equal to or different from brightness 1; this application does not limit its application. Optionally, brightness 3 may also be described as a first brightness.

[0135] The implementation process of S211 can be referred to the relevant description of S206 above. However, it is understandable that when adjusting the phone's display brightness via layers, the phone can continue to add layer 1 and set the transparency of layer 1 to a value of 2 (or transparency 2), which is greater than the value 1 set in the dozesuspend state described above. Alternatively, the phone can choose not to add layer 1, which is equivalent to setting the transparency of layer 1 to 1.

[0136] S212, The mobile phone displays the tabletop interface corresponding to the doze state 3.

[0137] The type of the display interface 3 (or the third interface) is the same as that of the display interface 2 mentioned above, to ensure the continuity of the screen display. For example, if the type of the display interface 2 is clock (i.e., the type of the second card included in the display interface 2 is clock), then the type of the display interface 3 can also be clock (i.e., the type of the first card included in the display interface 3 is clock). This is how the phone displays the above information when in dozesuspend mode. Figure 7 The tabletop setup interface is shown below. The mobile phone receives user clicks on the screen and, in response to the click, displays the following: Figure 6A or Figure 6B The display stand interface shown.

[0138] Alternatively, the type of the above-mentioned table setting interface 3 may not be the same as the type of the above-mentioned table setting interface 2. The table setting interface 3 may be the default interface displayed when entering the table setting function (i.e., the initial display interface), or the interface displayed in the last doze state (such as the above-mentioned table setting interface 1). This application does not impose any restrictions on the type of the table setting interface.

[0139] In this embodiment, when the electronic device switches from a dozesuspend state to a doze state, it needs to use the AP to draw the tabletop interface 3. The mobile phone can wake up the AP and use the GPU to draw the tabletop interface 3, realizing the display of the tabletop interface in the doze state, improving the interface's visual appeal, thereby enhancing the display effect, increasing its fun factor, and ultimately improving the user experience. Furthermore, on the one hand, the user is more likely to use the tabletop function while the phone is in the doze state, and the phone needs to respond to the user's trigger operations. On the other hand, the mobile phone has a higher frame rate in the doze state, and the phone needs to continuously draw the content in the tabletop interface 3 using the AP, i.e., update the tabletop interface 3. Therefore, during the doze state, the mobile phone can control the AP to be in a woken-up state.

[0140] In some embodiments, the above description uses a click operation as an example, that is, a touch event as a click event, to illustrate how to trigger the phone to switch from dozesuspend state to doze state. Of course, touch events can also be other types of events, such as swipe events. This application does not limit the type of touch event.

[0141] Optionally, in the dozesuspend state, when the phone first receives a touch event from the user, it only switches from the dozesuspend state to the doze state without executing the regular operation corresponding to that touch event. This regular operation can be understood as the operation performed by the phone in response to the touch event while in the doze state. Taking a swipe event as an example, in the doze state, a swipe event can trigger the phone to switch the type of the display screen. For instance, in the doze state, the phone might display something like... Figure 8 The clock-type interface shown in (a) is a timepiece. Afterwards, the phone receives a left swipe event from the user and, in response, displays the following: Figure 8 The display interface shown in (b) can be a personalized signature. For example, when a phone is in doze mode, it displays something like... Figure 9 The clock-type interface shown in (a) is a timepiece. Subsequently, in response to a user's swipe down input, the phone displays... Figure 9 The tabletop interface shown in (b) corresponds to the weather type.

[0142] Taking a touch event as a click event as an example, in doze mode, a click event can trigger the phone to display a close control. This close control is used to trigger the phone to exit the table setting function and stop displaying the table setting interface. For example, in doze mode, the phone displays something like... Figure 10 The setup interface is shown in (a). Afterwards, the phone receives a click from the user on the screen, and in response to the click, the phone displays as shown in (a). Figure 10 The tabletop interface shown in (b) includes a close control.

[0143] Additionally, it should be understood that after switching from dozesuspend state to doze state, if the phone receives a touch event from the user again, it can perform the normal operation corresponding to that touch event.

[0144] In some embodiments, similar to the optional steps S204, S205, and S206 described above when switching from the doze state to the dozesuspend state, S209, S210, and S211 are also optional steps when switching from the dozesuspend state to the doze state. The phone can execute one or more of steps S209, S210, and S211. It should be understood that the steps executed by the phone when switching from the dozesuspend state to the doze state are of the same type as those executed when switching from the doze state to the dozesuspend state. For example, when switching from the doze state to the dozesuspend state, the phone performs an AP sleep operation (i.e., S204) and reduces the display frame rate to frame rate 2 (i.e., S205). When switching from the dozesuspend state to the doze state, the phone performs an AP wake-up operation (i.e., S209) and increases the display frame rate to frame rate 3 (i.e., S210), without executing S211.

[0145] In some embodiments, when the mobile phone is in dozesuspend state, it can also automatically wake up the AP every time interval 2 (or the second time interval), such as 1 minute, to update the above-mentioned display screen 2, thereby updating the content of the display screen 2, thus avoiding screen burn-in and ghosting problems caused by the content displayed on the screen remaining static for a long time.

[0146] In one implementation, the mobile phone (such as the GPU in the phone) updates the positions of objects in the tabletop interface 2. For example, the tabletop interface 2 corresponds to a clock type. Every 2 seconds, the phone wakes up the AP (Application Processor) to utilize the GPU to update the time indicated by the clock, thereby shifting the positions of objects in the tabletop interface 2 and updating the interface. For instance, if time 2 is 1 minute, the phone enters a dozesuspend state and displays the above-described position. Figure 7 The setup interface is shown. After one minute, the phone wakes up the AP and updates. Figure 7 The position of the minute hand on the display screen shown. Figure 7 The minute hand initially points to the position corresponding to 34 minutes, but the updated minute hand indicates the position corresponding to 35 minutes.

[0147] In another implementation, the phone updates the images in the display interface 2. Each type of display interface corresponds to multiple images. The phone wakes up the AP every 2 seconds to use the AP to change the images in the display interface, thus updating the display interface 2. For example, if the display interface 2 corresponds to an electronic photo album type, the phone enters dozesuspend mode and displays... Figure 11 The display interface is shown in (a). Afterwards, every minute, the phone wakes up the AP and changes... Figure 11 The image in the tabletop interface shown in (a) is displayed as follows: Figure 11 The display stand interface shown in (b) is shown in the image. Figure 11 (a) and Figure 11 The tabletop display interfaces shown in (b) are all tabletop display interfaces 2, corresponding to the electronic photo album type. Figure 11 (a) and Figure 11 The image shown in (b) is different (here it can be replaced with a photograph).

[0148] In some embodiments, the AP can automatically enter a sleep state after updating the tabletop interface 2. Alternatively, after the mobile phone wakes up the AP at regular intervals 2, and after a certain period of time (or a third period), such as 2 seconds, it is determined that the tabletop interface 2 has been updated, and the mobile phone can control the AP to re-enter a sleep state to reduce power consumption.

[0149] It should be noted that S207-S212 described above are optional steps. After the phone is in dozesuspend state, it may not receive any user input trigger operation, and the phone may not switch from dozesuspend state to doze state.

[0150] In some embodiments, the above description illustrates how to run the table setting function when the phone meets the table setting entry conditions and its initial state is the doze state. Alternatively, when the phone meets the table setting entry conditions, it can also run the table setting function in the dozesuspend state initially. Then, upon receiving a user's trigger operation on the display screen, the phone can switch from the dozesuspend state back to the doze state, thus switching the standby state.

[0151] In some embodiments, the display driver in the mobile phone supports pulse adjustment. Compared to other applications the user uses on the phone, even when using the tabletop application, the user's gaze will not remain on the display screen continuously. Therefore, the phone can reduce the display effect to reduce power consumption. For example, when the phone launches the tabletop application, if the above-mentioned tabletop entry conditions are met, the phone can reduce the display driver's pulse from pulse1 (or the second pulse value) to pulse2 (or the first pulse value). pulse1 refers to the pulse value of the display driver when the phone is not running the tabletop function, i.e., the pulse value before launching the tabletop application. pulse2 refers to the pulse value of the display driver after launching the tabletop application. Both pulse1 and pulse2 are values ​​greater than 0, and pulse2 is greater than pulse1. For example, pulse1 is 16 and pulse2 is 4.

[0152] Alternatively, during the operation of the screen arrangement function, if the screen arrangement stop conditions are met, the phone can stop running the screen arrangement function and display the desktop or lock screen interface. The phone can also increase the display driver's pulse to pulse1 to improve display quality and ensure a better user experience. Of course, when the screen arrangement function is stopped, the phone can also set the display driver's pulse to a value greater than pulse2 instead of pulse1; this is not inherently restricted. The screen arrangement stop conditions can include at least one of the following: receiving a screen arrangement exit trigger operation (such as a user clicking the close control displayed on the phone), the phone's device state not being in landscape mode, and the phone's device state not being in a hover state.

[0153] In some embodiments, during the operation of the mobile phone's display function, the mobile phone can collect the current ambient light intensity (or ambient light intensity 1). The mobile phone determines whether ambient light intensity 1 meets a preset brightness adjustment condition (or a second preset condition). This preset brightness adjustment condition is used to trigger the mobile phone to adjust the brightness of the display screen. If the preset brightness adjustment condition is met, the mobile phone can adjust the brightness of the display screen to the target brightness corresponding to ambient light intensity 1, so that the display brightness of the mobile phone is adapted to the current ambient light intensity, improving the user experience.

[0154] If the preset brightness adjustment conditions are not met, the phone does not need to adjust the screen brightness based on the ambient light intensity 1.

[0155] Optionally, the aforementioned preset brightness adjustment conditions may include ambient light intensity 1 and ambient light intensity 2 belonging to different brightness adjustment ranges, or ambient light intensity 1 reaching a preset adjustment threshold. Ambient light intensity 2 represents the ambient light intensity collected by the mobile phone at the previous moment.

[0156] Optionally, if the phone is in dozesuspend mode and the preset brightness adjustment conditions are met, the phone needs to wake up the AP first, and then adjust the screen brightness to the target brightness corresponding to ambient light intensity 1. If the phone is in doze mode, the phone can directly adjust the screen brightness to the target brightness corresponding to ambient light intensity 1.

[0157] In some embodiments, the above description illustrates the process of a mobile phone running the table setting function by using different table setting interfaces corresponding to the doze state and the dozesuspend state as examples. Alternatively, the doze state and the dozesuspend state can also correspond to the same table setting interface. For example, the content of table setting interface 2 and table setting interface 1 described above is the same.

[0158] In some embodiments, the running state of the aforementioned table-setting application, i.e., the standby APP, is independent of the running state of the AP. Even if the AP is in sleep mode, the standby APP can still run normally and realize the table-setting function. The following will be combined with the above. Figure 4 The process of the standby app running is explained. For example... Figure 12 As shown, the process may include:

[0159] S1. When the mobile phone meets the conditions for setting up the table, the standby APP enters doze state.

[0160] S2. The standby APP sends request 1 to the AP. Request 1 is used to trigger the display of the tabletop interface 1 corresponding to the doze state.

[0161] S3. In response to the above request 1, the AP displays the tabletop interface 1 on the display screen through the display driver.

[0162] For example, the AP can first draw the tabletop interface 1 using the GPU, and then display the tabletop interface 1 on the display screen using the display driver.

[0163] In some embodiments, when the mobile phone meets the conditions for entering the display setup, it indicates that the mobile phone needs to run the display setup function. To reduce power consumption, the display driver can perform actions such as... Figure 13 In step S20, the display driver pulse is reduced from pulse1 to pulse2. Here, pulse1 can represent the display driver pulse before the phone meets the stage entry conditions.

[0164] Additionally, during standby app operation, users can trigger the phone to stop running the standby app when they no longer wish to use the tabletop function. For example, the standby app stops running when the phone meets the tabletop exit condition. The display driver upgrades the display driver's pulse from pulse2 to pulse1, thereby improving the phone's display performance.

[0165] The previous sections S1-S3 described the process by which the phone can run the table-setting function in a doze state beforehand. The implementation details of S1-S3 can be found in the descriptions of S201-S202 above. During the doze state, standby apps can switch from doze to dozesuspend to reduce the phone's power consumption. This switching process will be described below.

[0166] S4. If the time displayed on the above-mentioned tabletop interface 1 reaches time 1, and no trigger operation is received on the display screen within time 1, the standby APP switches from doze state to dozesuspend state.

[0167] S5. The standby APP receives the transparency information of the α layer sent by the brightness module.

[0168] The transparency information of the α layer indicates the transparency level of the α layer to be added. For example, this transparency information includes the value 1.

[0169] Optionally, the transparency information of the α layer mentioned above can be sent by the brightness module after receiving a relevant request from the standby APP.

[0170] S6. The standby APP sends request 2 to the AP. Request 2 includes the transparency information of the α layer.

[0171] In this context, request 2 is used to trigger the display of the tabletop interface 2 corresponding to the dozesuspend state, and to add layer α to the tabletop interface 2.

[0172] S7. In response to the above request 2, the AP displays the tabletop interface 2 on the display screen through the display driver.

[0173] S8 and AP use the display driver to draw an α layer with an transparency of 1 on the tabletop interface 2.

[0174] In this embodiment, the AP (e.g., the AP via GPU) draws the tabletop interface 2 and adds an α layer to the tabletop interface 2 to mask the tabletop interface, thereby reducing the display brightness of the mobile phone and thus reducing the power consumption of the mobile phone.

[0175] It should be noted that adding an α layer as described above is only one possible way to reduce the display brightness of a mobile phone. Standby apps can also reduce the display brightness of a mobile phone in other ways, and this application does not limit them.

[0176] S9, standby APP reduces the display's frame rate to 2 frames per second via the display driver.

[0177] For example, a standby app can send a request to the access point (AP), and the AP responds to the request by reducing the display's frame rate through the display driver.

[0178] S10, The standby APP sends request 3 to the AP.

[0179] Request 3 is used to trigger the AP to enter a sleep state.

[0180] S11. In response to the above request 3, the AP enters a sleep state.

[0181] For example, after the tabletop interface 2 and the above-mentioned α layer are drawn, the standby APP can trigger the AP to enter the sleep state without using the GPU, thereby reducing the power consumption of the phone.

[0182] In some embodiments, request 3 and request 2 are different requests. Alternatively, request 3 and request 2 are the same request, meaning that request 2 can also be used as request 3.

[0183] In some embodiments, such as Figure 13 As shown, during the dozesuspend state, to avoid screen burn-in and ghosting issues, the standby app can execute S21, sending a wake-up request to the AP every 2 hours. Upon receiving the wake-up request, the AP can execute S22, enter the wake-up state, and update the aforementioned tabletop interface 2, thus achieving periodic updates of the tabletop interface 2. Optionally, after updating the tabletop interface 2, the AP re-enters sleep mode.

[0184] In some embodiments, the phone's ambient light sensor driver can also report ambient light intensity so that a standby app can adjust the brightness of the phone's display screen based on the ambient light intensity. For example, such as... Figure 13 As shown, in step S23, the ambient light sensor driver acquires the ambient light intensity 1 collected by the ambient light sensor. Then, in step S24, if the ambient light intensity 1 meets the preset brightness adjustment conditions and the device is in a dozesuspend state, the ambient light sensor driver wakes up the application (AP). Then, the ambient light sensor driver can execute step S25, sending the ambient light intensity 1 to the standby application. After receiving the ambient light intensity 1, the standby application can determine the target brightness corresponding to it. Then, the standby application can execute step S26, sending the target brightness corresponding to the ambient light intensity 1 to the display driver. Then, the display driver can execute step S27, adjusting the display brightness to the target brightness.

[0185] It should be understood that the process of adjusting the brightness of the display screen according to the ambient light intensity 1 requires the use of upper-layer modules, such as the ambient light sensor driver, which needs to report the ambient light intensity 1 to the standby APP through the frame layer module corresponding to the ambient light sensor. Since the operation of the upper-layer module depends on the AP, the AP needs to be in a wake-up state.

[0186] Alternatively, the ambient light sensor driver can wake up the AP via a standby APP.

[0187] The sections S4-S11 above described the process by which the phone switches from the doze state to the dozesuspend state to reduce power consumption. The implementation details of S4-S11 can be found in the descriptions of S203-S206 above. While in the dozesuspend state, the phone can also switch back to the doze state based on user input. The following section will continue to describe the process of switching from the dozesuspend state to the doze state.

[0188] S12. The standby APP receives user click operations on the display screen.

[0189] S13. In response to the above click operation, the standby APP switches from dozesuspend state to doze state.

[0190] S14. The standby APP sends request 4 to the AP.

[0191] Request 4 is used to wake up the AP.

[0192] S15. In response to the above request 4, the AP enters the wake-up state.

[0193] S16. The standby APP sends request 5 to the AP. Request 5 is used to display the tabletop interface 3 corresponding to the doze state.

[0194] S17. In response to the above request 5, the AP displays the tabletop interface 3 on the display screen through the display driver.

[0195] S18, Standby APP increases the display frame rate to 3 frames per second via display driver.

[0196] In this embodiment, the AP does not add an α layer to the tabletop interface 3, resulting in higher display brightness on the phone and improved display effect, making it easier for users to use the tabletop function. Additionally, when the standby APP is in dozesuspend state, upon receiving a touch event from the user for the first time, it does not execute the regular operation corresponding to that touch event. Instead, it switches from dozesuspend state to doze state, increasing the phone's display brightness and preventing users from wondering why the phone did not respond after they input a touch event.

[0197] The above sections S12-S18 describe the process of the phone switching from dozesuspend state to doze state. The implementation process of S12-S18 can be referred to the relevant descriptions in S207-S212 above, and will not be repeated here.

[0198] It should be noted that the operations performed by the aforementioned modules (such as the brightness module, standby app, and display driver) and hardware (such as the AP) are merely examples. These operations can also be performed by other modules or hardware, and this application does not impose any restrictions on the modules or hardware performing these operations. Furthermore, it is understood that the operations performed by the aforementioned modules or hardware are actually performed by the mobile phone.

[0199] In some embodiments, 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 interface display method described above.

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

[0201] 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.

[0202] 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.

[0203] 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.

[0204] 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.

[0205] 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.

[0206] 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. A method for displaying an interface, characterized in that, Applied to electronic devices, the method includes: The first interface is displayed; wherein the first interface is the interface of the tabletop application; during the display of the first interface, the electronic device is in a first state; the first state indicates that the electronic device is in at least one of the following states: the frame rate of the display screen of the electronic device is a first frame rate, the application processor (AP) of the electronic device is in a wake-up state, and the display brightness of the electronic device is a first brightness; If no trigger operation is received on the electronic device within the first time period after the first time period, a second interface is displayed; wherein, the second interface is the interface of the tabletop application; during the display of the second interface, the electronic device is in a second state; the second state indicates that the electronic device is in at least one of the following states: the frame rate of the display screen is a second frame rate, the AP is in a sleep state, and the display brightness of the electronic device is a second brightness; The second frame rate is less than the first frame rate, and the second brightness is less than the first brightness.

2. The method according to claim 1, characterized in that, After displaying the second interface, the method further includes: Receive trigger operations on the display screen; In response to the triggering operation, a third interface is displayed; wherein the third interface is the interface of the tabletop application; during the display of the third interface, the electronic device is in the first state.

3. The method according to claim 2, characterized in that, The third interface includes a first card, and the second interface includes a second card. The first card and the second card are of the same type. The type includes at least one or more of the following: clock, weather, calendar, signature, and photo album.

4. The method according to claim 2 or 3, characterized in that, The third interface is different from the second interface. The third interface has animation effects, while the second interface does not.

5. The method according to any one of claims 1 to 4, characterized in that, When the second state indicates that the AP of the electronic device is in a sleep state, the method further includes: During the display of the second interface, the AP is controlled to enter the wake-up state every second time interval; The second interface is updated via the AP.

6. The method according to claim 5, characterized in that, After controlling the AP to enter the wake-up state, the method further includes: After the third time period, the AP is controlled to enter a sleep state.

7. The method according to any one of claims 1 to 6, characterized in that, Before displaying the first interface, the method further includes: The electronic device is determined to meet a first preset condition; wherein the first preset condition represents the condition for activating the tabletop application; the first preset condition includes the electronic device being in a first device state and the electronic device meeting at least one of the following conditions: the electronic device is in a stationary state for more than a fourth time, the electronic device is in a black screen state, the electronic device is in an Always On Display (AOD) state, and the electronic device is in a screen-on lock state; the first device state is a landscape state or a hover state.

8. The method according to claim 7, characterized in that, The method further includes: The display driver pulse of the electronic device is set to a first pulse value; wherein the first pulse value is less than a second pulse value, and the second pulse value refers to the display driver pulse value before the tabletop application is started.

9. The method according to any one of claims 1 to 8, characterized in that, If no trigger operation is received for the electronic device within the first time period, the method further includes: Adjust the brightness of the display screen to the second brightness; Alternatively, a first layer may be added to the second interface; wherein the display brightness of the electronic device displaying the second interface with the first layer added is the second brightness.

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: If the electronic device is in the first state and the current ambient light intensity meets the second preset condition, then the brightness of the display screen is adjusted based on the current ambient light intensity; the second preset condition indicates the condition that triggers the electronic device to adjust the brightness of the display screen. If the electronic device is in the second state, the AP is controlled to enter the wake-up state, and the brightness of the display screen is adjusted based on the current ambient light intensity.

11. The method according to any one of claims 1 to 10, characterized in that, The ambient light intensity when the electronic device displays the first interface is the same as the ambient light intensity when the electronic device displays the second interface.

12. An electronic device, characterized in that, The electronic device includes a memory, a display screen, and one or more processors; the memory, the display screen, and the processors are coupled; the memory is used to store computer program code, the computer program code including computer instructions; the display screen is used to display an image generated by the processor; when the processor executes the computer instructions, the electronic device performs the method as described in any one of claims 1 to 11.

13. 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 11.

14. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 11.

Images