Display method and electronic device

Abstract

The present application relates to the field of terminals, and provides a display method and an electronic device. The present application provides a display method applied to an electronic device, the electronic device having a first application installed therein, and the first application inheriting a low-power mode; the method comprising: when the electronic device is in a propped-up state, starting the first application; on the basis of a service interface displayed on a display screen under the control of the first application in a previous instance, the first application determining a target service interface to be displayed on the display screen under the control of the first application in a current instance, wherein a service interface adopted upon the first execution of the first application is determined by a service interface recommendation model; upon detecting that the electronic device is in a charging state, the first application, in an electronic device charging time period, controlling the display screen to display the target service interface; and upon detecting that the electronic device is not in a charging state, the first application, within a first preset duration, controlling the display screen to display the target service interface. The method of the present application enables an electronic device, when in a propped-up state, to display an application interface in a low-power mode.

Description

Display method and electronic equipment

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on January 10, 2024, with application number 202410045667.7 and application name “Display method and electronic device”, and claims priority to the Chinese patent application filed with the China Patent Office on January 10, 2024, with application number 202410045698.2 and application name “Display method and electronic device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of terminals, and in particular to a display method and electronic device. Background Art

[0003] With the continuous development of mobile terminal technology, mobile terminal applications are becoming increasingly widespread. When a user wishes to display images in a gallery while their phone is in the stand position, they are required to adjust the phone from portrait mode to the stand position. When the phone is in the stand position, the phone responds to the user's operation to launch the gallery and launches the gallery. The gallery application responds to the user's viewing operation and displays the user-selected image on the display screen.

[0004] However, displaying images from the gallery while the phone is in the stand requires multiple user actions, and the process of displaying images increases the phone's power consumption. If the phone is switched to a low-power standby mode to reduce power consumption, the apps on the phone will be in a sleep state, preventing them from displaying their interfaces properly. The challenge is how to display the user interface (e.g., playing a video file in a video app) while the phone is in the stand and low-power mode. Summary of the Invention

[0005] In order to solve the above technical problems, the present application provides a display method and electronic device, so that when the electronic device is in a stand state, the application interface can be normally displayed in a low-power state, thereby reducing the power consumption of the electronic device.

[0006] In the first aspect, the present application provides a display method, which is applied to an electronic device, in which a first application is installed, and the first application inherits a low power consumption mode; the method includes: when the electronic device is in a stand state, starting the first application; the first application determines the target service interface to be displayed on the display screen this time by the first application based on the service interface displayed on the display screen the last time the first application controlled the display screen, and the service interface used when the first application is first run is determined by a service interface recommendation model; when it is detected that the electronic device is in a charging state, the first application controls the display screen to display the target service interface during the charging period of the electronic device; when it is detected that the electronic device is not in a charging state, the first application controls the display screen to display the target service interface within a first preset time period.

[0007] In this way, an electronic device (such as a mobile phone, tablet computer, etc.) is installed with a first application (i.e., a smart display table), which inherits the low power mode, that is, the first application has the properties of the low power mode. In this example, when the electronic device is in the stand state, the first application is started, so that the electronic device is in a low power state, and the first application can control the display screen to adopt different display strategies in different scenarios under low power consumption, further reducing the power consumption of the electronic device. When the first application is run for the first time, the target service interface to be used in the first run can be determined based on the service interface recommendation model. The target service interface can be an image in the gallery application, a video file in the video application, or an interface of the calendar application; this allows the electronic device to view the required interface when the electronic device is in the stand state without the user having to perform multiple operations. For non-first application non-first run, the target service interface to be displayed on the display screen this time can be determined based on the service interface recorded in the last exit. This method enables the target service interface displayed on the display screen controlled by the first application to meet the needs of the user when the electronic device is in the stand state.

[0008] In addition, when the electronic device is in the stand state, if the electronic device is in the charging state, the target service interface can be displayed continuously during the charging period. Since the electronic device has sufficient power in the charging state, there is no need to limit the display time of the target service interface; when the electronic device is in the non-charging state, the first application can control the display screen to display the target service interface within a first preset time (such as 20 seconds, 30 seconds, etc.); avoid the electronic device displaying the target service interface for a long time, increase unnecessary power consumption of the electronic device, and thus further reduce the power consumption of the electronic device.

[0009] According to a first aspect, a first application includes: a state management module, a display module, and a timer; upon detecting that the electronic device is not in a charging state, the first application controls the display screen to display a target service interface for a first preset duration, including: upon detecting that the electronic device is not in a charging state, the display module controls the display screen to display the target service interface and starts the timer; upon detecting that the timer has reached the first preset duration, the display module transmits a first indication message to the state management module; and the state management module sets the display screen to switch to a screen-off state based on the first indication message. In this way, the first application can promptly control the display screen to enter the screen-off state through the timer and the state management module, and the power consumption of the first application running in the screen-off state is reduced, thereby reducing unnecessary power consumption.

[0010] According to the first aspect, after the display screen switches to the screen-off state, the method further includes: upon detecting a first preset event, the display module transmits second indication information to the state management module, where the first preset event includes a preset touch operation or an event in which a person gazes at the display screen; the state management module sets the display screen to light up based on the second indication information; and the display module instructs the timer to reset. Thus, since the screen-off state does not require exiting the first application, the electronic device further reduces power consumption after the display screen enters the screen-off state. In this example, the electronic device allows for responses to preset touch operations, allowing the first application to promptly display the target service interface without restarting the first application, thereby reducing power consumption.

[0011] According to the first aspect, the method further includes: within a first preset duration, when the display module detects a first preset event, instructing a timer to reset. The first preset event includes a preset touch operation or an event of human eye gaze at the display screen. Thus, if the first preset event is detected within the first preset duration, indicating that the user is viewing the target service interface, the timer is reset to extend the display duration of the target service interface, thereby preventing the display screen from entering a screen-off state while the user is viewing the target service interface, thereby affecting user experience.

[0012] According to the first aspect, the method further includes: within a first preset duration, when the display module detects a first preset event, increasing the timer threshold by a second preset duration, the first preset event including a preset touch operation or an event of human eye gaze at the display screen. Thus, if the first preset event is detected within the first preset duration, indicating that the user is viewing the target service interface, the timer threshold is increased, thereby extending the display duration of the target service interface, thereby preventing the display screen from entering a screen-off state while the user is viewing the target service interface, thereby affecting user experience.

[0013] According to a first aspect, an electronic device includes a power manager; the method further includes: when the power manager detects that the electronic device has switched to a screen-on state, controlling a first application to terminate execution, wherein the brightness of the display screen in the screen-on state is greater than the brightness of the target service interface displayed on the display screen controlled by the first application. In this way, when the electronic device switches to a screen-on state (e.g., when a mobile phone begins charging or a call is received), the power manager exits the low-power mode. This method can terminate the first application in a timely manner to avoid affecting the normal functions of the electronic device, such as affecting the display of a charging animation or a call interface.

[0014] According to the first aspect, the method further includes: in response to the electronic device being connected to or disconnected from the charger, switching the electronic device to a screen-on state. Thus, when the electronic device is connected to or disconnected from the charger, the screen-on state is switched to; and the power manager can promptly close the first application in the screen-on state.

[0015] According to the first aspect, the method further includes: in response to a user input operation of pressing a power button, the electronic device switches to a bright screen state. Thus, when the user presses the power button while the first application is running, the electronic device exits the low power consumption mode and enters the bright screen state. That is, when the user presses the power button, the power manager can close the first application to avoid affecting other operations.

[0016] According to a first aspect, upon detecting that an electronic device is in a charging state, before a first application controls a display screen to display a target service interface during the electronic device's charging period, the method includes: a display module detecting whether a first service function in the first application is enabled, the first service function being used to instruct the electronic device to allow the first application to control the display screen to display the target service interface during the charging period; and the display module detecting that the first service function is enabled. Thus, when the first service function is enabled, the display module displays the target service interface during the charging period, thereby improving the user's flexibility in controlling the duration of the display of the target service interface.

[0017] According to the first aspect, before starting the first application, the method further includes: when the system service of the electronic device detects that the electronic device is in the stand state, the system service detects whether a state value of the electronic device is a first value, the state value being used to indicate whether the electronic device meets a condition for allowing the first application to be started; when the system service detects that the state value is the first value, transmitting third indication information to a power manager of the electronic device to instruct the power manager to start the first application;

[0018] Starting the first application includes: the power manager starting the first application according to the third indication information. In this way, when the system service detects that the electronic device is in the stand state, it triggers the detection state value to determine whether it is the first value, and starts the first application in a timely manner.

[0019] According to the first aspect, the method further includes: registering a system service when the electronic device is powered on; the system service monitoring the status of each item to be monitored; and the system service determining and storing a status value of the electronic device based on the status of each item to be monitored. Thus, registering the system service when the electronic device is powered on allows the system service to monitor each item to be monitored in real time and promptly update the status value of the electronic device.

[0020] According to a first aspect, launching a first application includes: when a power manager detects that the electronic device has switched to a screen-off state, detecting whether a status value of the electronic device is a first value; and when the power manager detects that the status value of the electronic device is the first value, launching the first application. In this way, when the electronic device switches to a screen-off state, the power manager can promptly query the status value of the electronic device and promptly launch the first application.

[0021] According to the first aspect, the method further includes: obtaining preset monitoring items by the system service; obtaining service items supported by the electronic device by the system service; obtaining intersecting items between the preset monitoring items and the service items supported by the electronic device, and using the intersecting items as items to be monitored. This avoids the problem of inaccurate status values ​​caused by the electronic device not supporting certain preset monitoring items.

[0022] According to the first aspect, the preset monitoring items include: whether the account logged in by the electronic device is the account of the main user, whether the electronic device allows the first application to run, whether the electronic device has turned off the privacy moment service, whether the electronic device is in a stand state, whether the electronic device is in an unlocked state, whether the electronic device is not in a call state, whether the electronic device is not remotely locked, whether the electronic device is not in a power-on wizard state, whether the electronic device is not in a leather case mode, whether the electronic device is not in a virtual reality VR mode, and whether the electronic device is not in a power-saving mode.

[0023] According to the first aspect, if the service items supported by the electronic device include preset monitoring items; the system service determines the status value of the electronic device based on the status of each item to be monitored, including: when the system service detects that the account logged in to the electronic device is the account of the primary user, the electronic device allows the first application to run, the electronic device turns off the privacy moment service, the electronic device is in a stand state, the electronic device is in an unlocked state, the electronic device is not in a call state, the electronic device is not remotely locked, the electronic device is not in the power-on wizard state, the electronic device is not in a leather case mode, the electronic device is not in VR mode, and the electronic device is not in a power-saving mode, determining that the status value of the electronic device is a first value.

[0024] According to the first aspect, when the display module detects that the electronic device is not in a charging state, the display module controls the display screen to display the target service interface, including: when the first application is started, the first information of the electronic device is sent to the image synthesizer of the electronic device, the first information including fourth indication information and first identification information of the first application, the fourth indication information is used to instruct the image synthesizer to obtain the first display strategy; the image synthesizer determines that the image synthesizer adopts the first display strategy based on the first information; when the image synthesizer receives the first image to be displayed, the image synthesizer detects whether the first image belongs to the image sent by the first application according to the first display strategy; when the image synthesizer detects that the first image belongs to the image sent by the first application, the image synthesizer transmits the first image to the display screen, and the display screen displays the first image; when the image synthesizer detects that the first image does not belong to the image sent by the first application, the image synthesizer filters out the first image.

[0025] In this way, when the image synthesizer receives the fourth indication information, it can be determined that the image synthesizer needs to filter the received image, and the filtering strategy is the first display strategy (that is, the image sent by the first application is allowed to be displayed, and the images sent by other applications are filtered out). When the image synthesizer receives an image, the first display strategy can be used to filter out the images sent by other applications, and only the images sent by the first application are transmitted to the display screen. During the startup of the first application, if the image synthesizer first receives an image sent by other applications, the image synthesizer filters out the images sent by other applications due to the adoption of the first display strategy, thereby ensuring that the display screen will not display the images sent by other applications, thereby avoiding the problem of screen flickering on the display screen. In addition, the first display strategy is adopted when the first application is started, which can decouple the image displayed by the first application from the off-screen display (application).

[0026] According to a first aspect, an image synthesizer determines, based on first information, that it adopts a first display strategy, including: the image synthesizer obtains a first preset list based on fourth indication information; the image synthesizer adds first identification information to the first preset list; the first display strategy indicates to the image synthesizer that images belonging to the first preset list are permitted to be transmitted to the display screen. Thus, by adding the first identification information to the first preset list, the electronic device can accurately determine, based on tags in a received image and the first preset list, which images are permitted to be displayed.

[0027] According to a first aspect, an image synthesizer detects whether a first image belongs to an image sent by a first application based on a first display strategy, including: the image synthesizer obtains an image tag of the first image as a first tag, where the first tag is identification information of the application that generated the first image; the image synthesizer detects whether there is identification information identical to the first tag in a first preset list; when the image synthesizer detects that there is identification information identical to the first tag in the first preset list, it determines that the first image belongs to an image sent by the first application; when the image synthesizer detects that there is identification information identical to the first tag in the first preset list, it determines that the first image does not belong to an image sent by the first application. In this way, the first application can mark an image tag in a determined image. For example, the first application determines an interface for displaying a calendar, can obtain an image of the interface, and add a tag of the first application to the image; the image synthesizer compares the first tag in the first image with the identification information in the first preset list to quickly identify whether the first image belongs to an image sent by the first application.

[0028] According to the first aspect, the method further includes: when the first application terminates execution, obtaining setting information of the electronic device, the setting information being used to indicate information about services that the electronic device is allowed to start when in a low-power state; the first application sending fifth indication information to the image synthesizer based on the setting information; the image synthesizer obtaining the display strategy used by the image synthesizer based on the fifth indication information; and when the image synthesizer receives the second image, determining whether to transmit the second image to the display screen based on the currently determined display strategy. In this way, when the first application terminates execution, the display strategy of the image synthesizer can be determined based on the setting information of the electronic device, so that the currently used first display strategy can be promptly canceled to avoid affecting the display of other services.

[0029] According to the first aspect, the first application sends fifth indication information to the image synthesizer according to the setting information, including:

[0030] When the first application detects that the setting information indicates that the service allowed to run by the electronic device in a low-power state is the first service, fifth indication information is generated; the fifth indication information instructs the image synthesizer to adopt a second display strategy, and the second display strategy is used to instruct the image synthesizer to send the received image to the display screen; when the image synthesizer receives the second image, it determines whether to transmit the second image to the display screen according to the currently determined display strategy, including: when the image synthesizer receives the second image, it sends the second image to the display screen according to the instruction of the second display strategy. In this way, the first service can be a global display service in an off-screen display application, and the electronic device can store the information that allows the first service to run; when the first application ends its operation, if it detects that the electronic device allows the first service to run, it can instruct the image synthesizer to adopt a second display strategy, and the second display strategy indicates that images sent by other applications are allowed to be displayed, thereby avoiding the problem of filtering errors.

[0031] According to the first aspect, the first application sends fifth indication information to the image synthesizer according to the setting information, including:

[0032] When the first application detects that the setting information indicates that the service allowed to be started by the electronic device in a low-power state is a second service, fifth indication information is generated; the fifth indication information instructs the image synthesizer to adopt a third display policy, and the third display policy instructs the image synthesizer to allow the image sent by the second service to be transmitted to the display screen; when the image synthesizer receives the second image, the image synthesizer determines whether to transmit the second image to the display screen according to the currently determined display policy, including: when the image synthesizer receives the second image, according to the third display policy, whether the second image belongs to the image sent by the second service; when the image synthesizer detects that the second image belongs to the image sent by the second service, the image synthesizer transmits the second image to the display screen, and the display screen displays the second image; when the image synthesizer detects that the second image does not belong to the image sent by the second service, the image synthesizer filters out the second image. In this way, the second service can be a local display service in an off-screen display application; the policy corresponding to the local display service is the third display policy, that is, the image synthesizer filters out images that do not belong to the second service to prevent images sent by other applications from interfering with images sent by the second service.

[0033] According to the first aspect, the first application sends fifth indication information to the image synthesizer based on the setting information, including: when the first application detects that the setting information instructs the electronic device to run the screen-off service in a low-power state, the fifth indication information is generated, and the fifth indication information instructs the image synthesizer to adopt the fourth display strategy, and the fourth display strategy instructs the image synthesizer to prohibit the transmission of the received image to the display screen; when the image synthesizer receives the second image, it determines whether to transmit the second image to the display screen according to the currently determined display strategy, including: when the image synthesizer receives the second image, it filters out the second image according to the fourth display strategy instruction. In this way, the strategy corresponding to the screen-off service is the fourth display strategy, that is, the image synthesizer filters out images sent by any application, so that the electronic device will not display images of other applications in the screen-off state, thereby reducing the power consumption of the electronic device.

[0034] According to the first aspect, the services that are allowed to be started when the electronic device is in a low-power state include a first service, a second service, and a screen-off service; when the first service is started, the first service controls the display screen to display a first preset image when the electronic device is in a locked screen state, and the brightness of the display screen when displaying the first preset image is less than a first brightness, which is the brightness of the display screen when the electronic device is in a normal operating state; when the second service is started, the second service controls the display screen to display a second preset image in a first area of ​​the display screen when the electronic device is in a locked screen state, and the first display area is smaller than the area of ​​the display screen, and the brightness of the display screen when displaying the second preset image is less than the first brightness. In this way, the power consumption of the first and second services in displaying images is low.

[0035] In a second aspect, the present application provides a chip system, including a processor, for calling and running a computer program from a memory, so that an electronic device equipped with the chip system executes the display method corresponding to the first aspect and any implementation method of the first aspect.

[0036] In a third aspect, the present application provides an electronic device comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device executes the display method corresponding to the first aspect and any one of the implementation methods of the first aspect.

[0037] The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can be referred to the technical effects corresponding to the first aspect and any implementation of the first aspect, and will not be repeated here.

[0038] In a fourth aspect, the present application provides a computer-readable medium for storing a computer program. When the computer program is run on an electronic device, the electronic device executes the display method corresponding to the above-mentioned first aspect and any one of the implementation methods of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0040] FIG1 is a schematic structural diagram of an electronic device;

[0041] FIG2 is a block diagram of a software structure of an electronic device;

[0042] FIG3 is a schematic diagram illustrating an exemplary setting interface of a smart table;

[0043] FIG4 is a schematic diagram showing four exemplary scenarios for triggering the activation of a smart table;

[0044] FIG5 is a schematic diagram showing an example of a target service interface displayed on a smart table control display screen;

[0045] FIG6 is a schematic diagram showing an example of an electronic device turning on a smart display;

[0046] FIG7 is a schematic diagram showing another exemplary embodiment of an electronic device turning on a smart display;

[0047] FIG8 is a flowchart illustrating an example of an electronic device determining that the electronic device meets the requirements for enabling the smart display;

[0048] FIG9 is a schematic diagram showing an exemplary scenario of an electronic device turning on a privacy moment;

[0049] FIG10 is a flowchart illustrating an example of a smart display table using different display strategies;

[0050] FIG11 is an exemplary diagram showing a scene of a smart table controlling a display screen to display a target service interface;

[0051] FIG12 is an exemplary diagram showing another scenario of a smart table controlling a display screen to display a target service interface;

[0052] FIG13 is a diagram showing another exemplary scenario of a smart table controlling a display screen to display a target service interface;

[0053] FIG14 is a diagram showing another exemplary scenario of a smart table controlling a display screen to display a target service interface;

[0054] FIG15 is a diagram showing another exemplary scenario of a smart table controlling a display screen to display a target service interface;

[0055] FIG16 is a diagram showing another exemplary scenario of a smart table controlling a display screen to display a target service interface;

[0056] FIG17 is a diagram showing another exemplary scenario of a smart table controlling a display screen to display a target service interface;

[0057] FIG18 is a diagram showing another exemplary scenario of a smart table closing application;

[0058] FIG19 is a schematic diagram illustrating an exemplary setting interface for screen-off display;

[0059] FIG20 is a schematic diagram exemplarily showing a screen flashing in an electronic device;

[0060] FIG21 is a flow chart showing an exemplary display method;

[0061] FIG22 is a flow chart showing an exemplary display method;

[0062] FIG23 is a schematic diagram exemplarily showing layers displayed on a display screen;

[0063] FIG24 is a schematic diagram showing an exemplary smart table display target service interface. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0065] The term "and / or" in this article is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0066] In the description and claims of the embodiments of this application, the terms "first" and "second" are used to distinguish different objects, rather than to describe a specific order of objects. For example, the terms "first target object" and "second target object" are used to distinguish different objects, rather than to describe a specific order of objects.

[0067] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0068] In the description of the embodiments of this application, unless otherwise specified, "multiple" means two or more. For example, "multiple processing units" means two or more processing units; "multiple systems" means two or more systems.

[0069] Before explaining the embodiments of the present application in detail, the application scenarios in the present application are first explained. If the user needs to watch a movie when the mobile phone is in the stand state, the user needs to click on the icon of the video application, and the mobile phone starts the video application in response to the user's click operation. The video application plays the movie in response to the user clicking on the icon of the movie to be watched. The video application switches the movie video to horizontal playback in response to the user clicking on the horizontal screen play button. After switching the movie video to horizontal playback, the user needs to adjust the mobile phone from the portrait state to the stand state to watch the movie video. The above process requires the user to perform multiple operations, and the operation steps are cumbersome. Moreover, the normal playback of the video by the mobile phone in the stand state results in high power consumption of the mobile phone. If the mobile phone is adjusted to a low power consumption state (such as in the screen-off state), the application in the mobile phone will enter a sleep state, and the display screen will not be able to play videos or display the application interface normally.

[0070] In order to reduce the user's operating steps and reduce the power consumption of the interface of the application displayed in the stand state. The present application provides an application of a smart stand (hereinafter also referred to as Standby), which inherits the Doze mode (i.e., low power mode). The smart stand is installed on an electronic device, which may be a mobile phone, tablet computer or other device. After the smart stand is started, it can determine the service interface of the recommended application (such as photos in the gallery application) based on the location, time and other information of the electronic device, and control the display screen to display the determined service interface. There are many ways for an electronic device to determine a service interface. For example, a service interface recommendation model may be pre-stored in a mobile phone. The input information of the service interface recommendation model may be the location information, time information, etc. of the mobile phone. The output information is the service interface to be recommended. The model may adopt a deep learning network, and the specific training process of the model will not be repeated here.

[0071] FIG1 is a schematic diagram of the structure of an electronic device 100 shown in an embodiment of the present application. It should be understood that the electronic device 100 shown in FIG1 is only an example of an electronic device, and the electronic device 100 may have more or fewer components than shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in FIG1 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits. In this example, the electronic device 100 takes a mobile phone as an example.

[0072] The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

[0073] Figure 2 is a block diagram of the software structure of the electronic device 100 according to an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and divisions of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the hardware abstraction layer (HAL), and the kernel layer.

[0074] The application layer can include a series of application packages. As shown in Figure 2, the application package can include applications such as smart display, camera, gallery, calendar, video, etc.

[0075] The application framework layer provides an application programming interface (API) and programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

[0076] As shown in FIG2 , the application framework layer may include a window manager, a power manager, system services, a notification manager, a phone manager, a view system, a resource manager, and the like.

[0077] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc. In this application, the window manager is used to manage the interface display of the smart display.

[0078] The power manager is used to manage the DreamService in the low power mode of the Android system. For example, the power manager can control the electronic device to start the DreamService and exit the DreamService.

[0079] The system service (SystemServer) can monitor the status of each item to be monitored, and determine whether the electronic device meets the conditions for starting the smart display according to the status of each item to be detected.

[0080] The phone manager is used to provide communication functions of the electronic device 100, such as management of call status (including answering, hanging up, etc.).

[0081] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0082] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, etc. The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify the completion of downloads, message reminders, etc. The notification manager can also be a notification that appears in the status bar at the top of the system in the form of an icon or scroll bar text, such as notifications from applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, it can prompt text information in the status bar, emit a prompt sound, vibrate the electronic device, flash the indicator light, etc.

[0083] HAL can include an image compositor (SurfaceFlinger), a surface manager (surface manager), and media libraries (Media Libraries). SurfaceFlinger is a system service used to render images drawn by applications and send the rendered images to the display for display.

[0084] The kernel layer is the layer between hardware and software. The kernel layer includes at least the TP (Touch Panel) driver, device motion module (Device Motion), display driver, Bluetooth driver, audio driver, and Wi-Fi driver.

[0085] TP driver can provide touch events for electronic devices with low power consumption.

[0086] DeviceMotion provides algorithmic logic for electronic devices to maintain a stand state. For non-folding screens, the stand state is defined as the angle between the short axis of the device and the horizontal plane being between 30 and 90 degrees. For folding screens, the stand state is defined as the display screen being between a fully extended and folded state.

[0087] It is understood that the application layer, application framework layer, HAL, and components included in the kernel layer shown in FIG2 do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or combine or split some components, or arrange the components differently.

[0088] In some embodiments, the smart display in the electronic device is in an off state by default. When the user needs to use the function of the smart display, the electronic device can be allowed to start the smart display. For example, the user can click on the smart display option in the setting interface, and the mobile phone responds to the user's click operation and jumps to the smart display setting interface, which is shown as interface 301 in Figure 3. The smart display setting interface 301 includes option 302, and the option 302 includes switch 3021. In response to the user's operation of clicking switch 3021, the mobile phone allows the electronic device to start the smart display when it detects that the conditions for starting the smart display are met.

[0089] When the user turns on the switch 3021 in the smart display setting interface, the electronic device can monitor in real time whether the electronic device currently meets the conditions for starting the smart display. When the electronic device monitors that the electronic device currently meets the conditions for starting the smart display, the smart display is started.

[0090] In order to facilitate understanding of the smart display table, the functions of the smart display table are described in detail below with reference to FIG4 and FIG5 .

[0091] When the electronic device detects that the electronic device is in the stand state, it can trigger the electronic device to monitor whether the conditions for turning on the smart display are currently met. In this example, the electronic device takes a mobile phone as an example. Figure 4 exemplifies four scenarios when the electronic device is in the stand state. As shown in 4a in Figure 4, the mobile phone is in the state of bright screen and locked screen; as shown in 4b in Figure 4, the mobile phone is in the state of always on display (AOD). As shown in 4c in Figure 4, the mobile phone is in the state of off screen; as shown in 4d in Figure 4, the mobile phone is in the state of bright screen and on the desktop.

[0092] When the mobile phone detects that the conditions for starting the smart display are currently met, the smart display is started. When the mobile phone starts the smart display for the first time, the smart display can display recommended content on the display screen based on the service interface recommendation model. When the mobile phone exits the smart display, the service interface information last displayed by the smart display can be recorded. The information of the service interface may include the identification information of the application to which the interface belongs. For example, if the smart display last displayed the calendar interface, the mobile phone can record the package name of the calendar; if the smart display last displayed the gallery, when the mobile phone exits the smart display, the package name of the gallery can be recorded.

[0093] When the mobile phone does not start the smart display for the first time, the smart display can obtain the information of the service interface displayed by the smart display last time. The smart display determines the target service interface based on the information of the service interface displayed last time, and displays the target service interface on the display screen. If the smart display detects that the service interface displayed last time belongs to the gallery or video application, the smart display requests the user to authorize access rights. After the smart display receives the access rights authorized by the user, the smart display can display images in the gallery or play videos in the video application. If the smart display detects that the service interface displayed last time belongs to the calendar, the calendar interface can be displayed directly on the display screen. In other words, when the smart display detects that the service interface displayed last time contains the user's privacy data (such as the user's photo album, watched video information, etc.), it needs to obtain the user's authorized access rights.

[0094] FIG5 is a schematic diagram showing an exemplary scene displayed by a smart display table.

[0095] As shown in 5a in Figure 5, assuming that the mobile phone starts the smart display application for the first time, the smart display determines the interface of the calendar displayed on the display screen based on the service interface recommendation model (such as 501 in 5a in Figure 5). In another example, assuming that the smart display last displayed an image in the gallery, the smart display records the information of the service interface displayed last time. The information of the service interface indicates that the image displayed last belongs to the gallery, and the mobile phone can obtain the access rights authorized by the user. For example, after the smart display is started, it determines that the target service interface is the interface of the gallery. Before obtaining the access rights, the smart display indicates that the image with a mask is displayed on the display screen, and asks the user whether to authorize access to the gallery. When the mobile phone receives the access rights authorized by the user, the image in the gallery is displayed on the display screen, such as 502 in 5b in Figure 5.

[0096] Optionally, assuming that the smart display last displayed an image in a video application, the smart display records the image information of the last display, and the image information indicates that the last displayed image belongs to a video application. After the mobile phone obtains the access rights authorized by the user, it can play the video that the user watched last on the display screen.

[0097] Optionally, when the smart display stand is running, since the smart display stand inherits the Doze mode, that is, the smart display stand runs when the mobile phone is in low power consumption, the smart display stand controls the brightness of the display interface to be lower than the brightness of the image displayed by the mobile phone in normal operating state, so as to reduce power consumption.

[0098] The following specifically describes a process of activating a smart display by an electronic device with reference to FIG6 . In this example, a mobile phone is used as an example of an electronic device. The process of activating the smart display by the mobile phone includes:

[0099] Step 601: When the mobile phone is turned on, the mobile phone registers with the SystemServer.

[0100] Specifically, when the mobile phone is turned on, it can register with the system service so that the system service can monitor the status of each item to be monitored in real time.

[0101] Step 602: SystemServer monitors the conditions for the smart display to be enabled and writes the status value into the database.

[0102] Specifically, the various monitoring items of the smart display stand can be determined based on the functions supported by the mobile phone and the preset monitoring items. The mobile phone obtains the preset monitoring items and the functions supported by the mobile phone, obtains the items that intersect the preset monitoring items and the functions supported by the mobile phone, and uses the intersecting items as the items to be monitored. For example, the preset monitoring items include: detecting whether the account logged into the mobile phone is the account of the main user, whether the switch of the smart display stand is turned on, whether the mobile phone is in a private moment, whether it is in a stand state, whether it is in a low power state, whether the mobile phone is unlocked, whether the mobile phone is remotely locked, whether the mobile phone is in the power-on wizard state, whether the mobile phone is in a leather case mode, whether the mobile phone is not in VR mode, and whether the mobile phone is not in a power-saving mode. If the functions supported by the mobile phone all include the above-mentioned preset monitoring items, it is determined that the items to be monitored include the above-mentioned 12 preset monitoring items.

[0103] For example, if the mobile phone does not support the remote locking function or the VR mode, the items to be monitored include: detecting whether the account logged in by the mobile phone is the account of the main user, whether the switch of the smart display is turned on, whether the mobile phone is in the privacy moment, whether the mobile phone is in the stand state, whether the mobile phone is in a low-battery state, whether the mobile phone is unlocked, whether the mobile phone is in the power-on wizard state, whether the mobile phone is in the leather case mode, and whether the mobile phone is not in the power-saving mode.

[0104] In one example, after a mobile phone registers with the SystemServer, the SystemServer monitors the status of each monitored item in real time and records the status value of the current electronic device. The status value is used to indicate whether the mobile phone currently meets the conditions for allowing startup. For example, the status value may include "0" and "1". When the status value is "1" (i.e., the first value), the status value indicates that the current mobile phone meets the conditions for allowing the startup of the smart display; when the status value is "0" (i.e., the second value), the status value indicates that the current mobile phone does not meet the conditions for allowing the startup of the smart display.

[0105] In one example, when SystemServe detects a change in the status of any monitored item, it updates the stored status value of the phone. If the phone detects that the screen is both on and locked (as shown in 4a in Figure 4), and SystemServer detects that the phone is in the stand, it triggers SystemServer to detect the status of each item to be detected to determine whether the phone meets the conditions for enabling the smart display.

[0106] FIG8 is a flowchart showing an example of an electronic device determining that the electronic device meets the requirements for enabling the smart display. As shown in FIG8 , the process includes:

[0107] Step 801: System Server determines whether it is the primary user. If so, execute step 802; if not, end the determination process.

[0108] Specifically, the SystemServer determines whether the account logged in by the mobile phone is the account of the primary user. For example, the SystemServer of the Honor mobile phone can detect whether the Honor account currently logged in by the mobile phone is the user account when the user registered (ie, the primary user).

[0109] If the SystemServer determines that the account logged in by the mobile phone is not the account of the main user, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the activation of the smart display, and the mobile phone is not allowed to activate the smart display.

[0110] If the System Server determines that the account logged in by the mobile phone is not the account of the primary user, it can continue to determine the next item. For example, in this example, the System Server executes step 802.

[0111] Step 802: System Server determines whether the switch of the smart display is turned on. If so, execute step 803; if not, end the judgment process.

[0112] Specifically, the SystemServer determines whether the switch of the smart display is turned on, that is, detects whether the electronic device allows the electronic device to start the smart display when it detects that the conditions for starting the smart display are met. For example, the SystemServer can detect whether the switch in the interface shown in Figure 3 is turned on. If it is detected that it is turned on, the SystemServer determines the next item; if it is detected that it is not turned on, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started, and the smart display is not allowed to be started.

[0113] Step 803: System Server determines whether the privacy moment service is closed. If so, step 804 is executed; if not, the determination process ends.

[0114] Specifically, the SystemServer determines whether the mobile phone has turned off the Privacy Moment service. If it is detected that the mobile phone has turned off the Privacy Moment service, the SystemServer determines the next item; if it is detected that the mobile phone has turned on the Privacy Moment service, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started.

[0115] In some examples, a mobile phone has a Private Moment service. When the Private Moment service is activated, the phone will prohibit applications from accessing the microphone, prohibiting applications from calling the camera function, prohibiting applications from obtaining the phone's current geographic location information, prohibiting the phone from connecting to Wi-Fi networks, etc. The user can activate the Private Moment service in the phone's navigation bar. As shown in Figure 9, the phone screen displays a navigation bar 901. The user clicks the Private Moment service icon 902. The phone responds to the user's click and activates the Private Moment service.

[0116] Step 804: System Server determines whether it is in the support state. If so, execute step 805; if not, end the determination process.

[0117] Specifically, the SystemServer determines whether the mobile phone is currently in the stand state. The SystemServer can obtain the status of the mobile phone detected by DeviceMotion; if it is detected that the mobile phone is currently in the stand state, the SystemServer determines the next item; if it is detected that the mobile phone is not currently in the stand state, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started.

[0118] In this example, DeviceMotion can detect whether the phone is in a stand state. When the phone's display screen is a non-folding screen, DeviceMotion can detect whether the angle between the phone's short axis and the horizontal plane is between 30 and 90 degrees. If it is detected that it is, it can be determined that the phone is in a stand state. When the phone's display screen is a folding screen, DeviceMotion can detect whether the display screen is in a state between a folded state and an unfolded state. If it is detected that it is, it is determined that the phone is in a stand state. Optionally, DeviceMotion can also use other conditions to determine whether the phone is in a stand state, which are not listed here one by one.

[0119] Step 805: The System Server determines whether the battery is not in a low power state. If so, step 806 is executed; if not, the determination process ends.

[0120] Specifically, the SystemServer can obtain the current battery level of the mobile phone. When it detects that the current battery level of the mobile phone is greater than the preset battery threshold, it determines that the mobile phone is not in a low-battery state, and the SystemServer can continue to judge the next item. The preset battery threshold can be a value less than 50%, for example, the battery threshold is 35%, 30%, 25%, etc. When the SystemServer detects that the current battery level of the mobile phone is less than or equal to the preset battery threshold, it determines that the mobile phone is currently in a low-battery state. The SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started.

[0121] Step 806: System Server determines whether the mobile phone is unlocked. If so, execute step 807; if not, end the determination process.

[0122] Specifically, the SystemServer obtains the unlocking status of the mobile phone. When it detects that the mobile phone is unlocked, it can continue to judge the next item; when it detects that the mobile phone is not unlocked, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started.

[0123] Step 807: System Server determines whether the mobile phone is not in a call state. If so, step 808 is executed; if not, the determination process ends.

[0124] Specifically, the SystemServer obtains the call status of the mobile phone. When it detects that the mobile phone is not in a call state, it can continue to judge the next item; when it detects that the mobile phone is in a call state, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started.

[0125] Step 808: System Server determines whether the mobile phone is not remotely locked. If so, execute step 809; if not, end the determination process.

[0126] Specifically, the SystemServer obtains the remote lock status. When it detects that the phone is in the remote lock state, the SystemServer can update the status value in the database to "0" to indicate that the phone does not meet the conditions for allowing the smart display to be activated. When it detects that the phone is not in the remote lock state, the SystemServer continues to determine the next item.

[0127] Step 809: The System Server determines whether the mobile phone is not in the startup wizard state. If so, step 810 is executed; if not, the determination process ends.

[0128] Specifically, when the System Server detects that the mobile phone is in the boot wizard state, the System Server can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be started. When it is detected that the mobile phone is not in the boot wizard state, the System Server continues to determine the next item.

[0129] Step 810: System Server determines whether the mobile phone is not in the leather case mode. If so, step 810 is executed; if not, the determination process ends.

[0130] Specifically, when the SystemServer detects that the phone is in leather case mode, it can update the status value in the database to "0" to indicate that the phone does not meet the conditions for enabling smart display. If it detects that the phone is not in leather case mode, the SystemServer proceeds to the next item. Leather case mode allows the phone to display information adaptively based on the leather case after it is installed.

[0131] Step 811: System Server determines whether the mobile phone is not in VR mode. If so, execute step 812; if not, end the determination process.

[0132] Specifically, when the System Server detects that the mobile phone is in VR mode, the System Server can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the activation of the smart display. When it is detected that the mobile phone is not in VR mode, the System Server continues to determine the next item.

[0133] Step 812: System Server determines whether the mobile phone is not in power saving mode. If so, it determines that the current mobile phone meets the conditions for allowing the activation of the smart display; if not, the determination process ends.

[0134] Specifically, when the SystemServer detects that the mobile phone is in power saving mode, the SystemServer can update the status value in the database to "0" to indicate that the mobile phone does not meet the conditions for allowing the smart display to be activated. When it is detected that the mobile phone is not in power saving mode, the SystemServer can update the status value in the database to "1" to indicate that the mobile phone currently meets the conditions for allowing the smart display to be activated.

[0135] It should be noted that after the System Server obtains the items to be monitored of the mobile phone, the order of judging the items to be monitored may be different; when the System Server detects that all the items shown in FIG8 meet the conditions, it is determined that the mobile phone meets the conditions for allowing the smart display to be started.

[0136] In addition, when the SystemServer detects that the mobile phone is in the stand state and triggers the SystemServer to detect the status of each item to be detected, the SystemServer can perform 12 judgments in sequence according to the judgment method shown in Figure 8 to prevent the mobile phone from changing from the stand state to other states (such as vertical screen state) during the judgment process.

[0137] Step 603: When the SystemServer detects that the status value indicates starting the smart display, it instructs the power manager to start the smart display.

[0138] Specifically, when the SystemServer detects that the mobile phone is in the stand state, it triggers the SystemServer to detect whether the status value in the database is the first value. When the SystemServer detects that the status value in the database is the first value, it can instruct the power manager to pull up the smart display. The first value is used to indicate that the mobile phone meets the conditions for allowing the smart display to be started, and the second value is used to indicate that the mobile phone does not meet the conditions for starting the smart display. For example, when the SystemServer detects that the status value in the database is updated from "0" to "1", it instructs the power manager to start the smart display.

[0139] Step 604: The power manager starts the DreamService in the smart display.

[0140] Specifically, the Smart Display is an application that inherits from Doze mode. Doze mode has a DreamService, which is used to display specific content when the phone is idle, charging, or locked. Therefore, in this example, the power manager starting the Smart Display can be understood as the power manager launching the DreamService of the Smart Display.

[0141] Step 605: After the smart table is started, register the database.

[0142] Specifically, after the power manager starts the smart display, the smart display can register with the database to monitor changes in status values ​​stored in the database.

[0143] Step 606: The smart table monitors the status value in the database.

[0144] Specifically, after the smart display unit registers with the database, it can monitor the changes of the status value in the database in real time. When the smart display unit detects that the status value in the database changes from a first value to a second value, step 607 can be executed.

[0145] It should be noted that when the smart display is activated, it can also obtain information about the service interface that was last displayed by the smart display. Based on the information about the service interface that was last displayed, the smart display determines the target service interface and displays it on the display screen. The process of the smart display determining the target service interface can be referred to the relevant description in Figure 5 and will not be repeated here.

[0146] Step 607: When the smart display detects that the status value indicates exiting the smart display, the display screen is controlled to switch to a bright screen state.

[0147] Specifically, when the smart display detects that the state value is updated to the second value, the smart display controls the electronic device to switch to a bright screen state. In this example, the bright screen state is a state in which the display screen of the mobile phone displays an interface in a normal mode.

[0148] Step 608: The power manager detects that the display screen is in the on-screen state and exits DreamService.

[0149] Specifically, when the power manager detects that the display screen is in the on-screen state, it exits the Doze state, that is, exits the DreamService of Standby.

[0150] Step 609: The smart table setting ends.

[0151] Specifically, the power manager exits the DreamService of Standby, that is, controls the smart table to stop running.

[0152] In some embodiments, if the user performs a screen-off operation or the phone is in a timeout period, the phone will switch to the screen-off state. After the power manager detects that the phone has switched to the screen-off state, it can trigger the power manager to obtain the status value from the database to determine whether to pull up the smart display. The timeout screen-off instruction indicates that the phone switches to the screen-off state after detecting no touch operation within a third preset time period.

[0153] FIG7 specifically illustrates the process of starting the smart table by triggering the power manager, which includes:

[0154] Step 701: When the mobile phone is turned on, the mobile phone registers with the SystemServer.

[0155] Step 702: SystemServer monitors the conditions for the smart display to be enabled and writes the status value into the database.

[0156] The process of step 701 to step 702 can refer to the relevant description of step 601 to step 602, which will not be repeated here.

[0157] Step 703: When the user performs a screen-off operation, the power manager detects that the phone screen is off and obtains a status value from the database.

[0158] Specifically, in response to a user screen-off operation (such as pressing the power button), the mobile phone performs a screen-off operation, and the mobile phone is in the screen-off state. Optionally, when the mobile phone detects no user operation within a third preset time period (such as 30 seconds, 1 minute, 5 minutes, etc.), the screen-off operation is performed, and the mobile phone is in the screen-off state. When the power manager detects that the mobile phone is in the screen-off state, it obtains the status value of the mobile phone from the database.

[0159] Step 704: When the power manager detects that the status value indicates that the smart display is to be started, it starts the DreamService in the smart display.

[0160] Specifically, when the power manager detects that the status value (such as the status value is "1") indicates that the smart display is started, the power manager pulls up the smart display.

[0161] If the power management detects that the status value is "0", the image can be displayed according to the AOD display policy or wallpaper display policy. In other words, when the power manager detects that the phone is switched to the off-screen state, the power manager first determines whether the conditions for starting the smart display are met.

[0162] Step 705: After the smart display is started, register the database.

[0163] Step 706: The smart table monitors the status value in the database.

[0164] Step 707: When the smart display detects that the status value indicates exiting the smart display, the display screen is controlled to switch to a bright screen state.

[0165] Step 708: The power manager detects that the display screen is in the on-screen state and exits DreamService.

[0166] Step 709: The smart table setting ends.

[0167] The above-mentioned steps 705 to 709 can refer to the relevant descriptions in steps 605 to 609, which will not be repeated here.

[0168] Figures 6 and 7 above specifically illustrate two processes of triggering a mobile phone to start the smart table setting.

[0169] The following uses Figure 10 to illustrate that the smart display table uses different display strategies to display the target service interface in different scenarios.

[0170] As shown in Figure 10, the Smart Display includes a state management module, a display module, and a timer. The state management module manages the screen on and off when the Smart Display is enabled. In this example, the state management module can turn the screen on and off by inheriting the DreamService in the Doze state.

[0171] Step 1001: The state management module enters the Doze state.

[0172] Specifically, since the smart display inherits the Doze mode in Android, when the smart display is started, the state management module enters the Doze state. When the state management module enters the Doze state, it instructs the display module to enter a low power consumption state.

[0173] Step 1002: The display module obtains an image of the smart display table.

[0174] Specifically, after receiving instructions from the status management module, the display module obtains the target image to be displayed. The display module can also obtain information about the service interface last displayed by the smart display. Based on the information about the service interface last displayed, the display module determines the target service interface. The process by which the display module determines the target service interface can be seen in the relevant description of FIG. 5 and will not be further elaborated here.

[0175] Step 1003 : The display module determines whether the switch of the permanent display is turned on. If it is detected that it is turned on, step 1004 is executed; if it is detected that the switch of the permanent display is not turned on, step 1006 is executed.

[0176] Specifically, the application interface of the smart display table may include a switch for always displaying (i.e., a switch for the first service function). When the switch for always displaying is turned on, it indicates that when the mobile phone is in a charging state, the display module is allowed to control the display screen to always display the target service interface during the charging period. When the switch for always displaying is turned off, it indicates that when the mobile phone is in a charging state, the display module is not allowed to control the display screen to always display the target service interface during the charging period.

[0177] In this example, when it is detected that the switch of the permanent display is turned on, it is possible to continue to determine whether the mobile phone is in a charging state. When it is detected that the switch of the permanent display is turned off, step 1006 can be executed.

[0178] Step 1004: The display module determines whether the mobile phone is in a charging state. If it is detected that the mobile phone is in a charging state, step 1005 can be executed; if it is detected that the mobile phone is not in a charging state, step 1006 is executed.

[0179] Specifically, if the display module detects that the phone is in a charging state and the always-on display switch is turned on, the display module controls the display screen to continuously display the target service interface during the charging period. If the display module of the smart display responds to the user turning off the always-on display switch or detects that the phone is not in a charging state, the display module may execute step 1006.

[0180] Step 1005: The display module displays the image determined by the smart display in the charging state.

[0181] Specifically, when the mobile phone is in a charging state and the always-on display switch is turned on, the display screen controls the display screen to display the target service interface during the charging period.

[0182] Step 1006: The display module starts a timer.

[0183] Specifically, when the display module detects that the always-on display switch of the smart display stand is not turned on or the mobile phone is not in a charging state, the display module can display a target image and instruct a timer to start timing. The timing threshold of the timer can be a first preset duration, for example, the first preset duration is 20 seconds, 25 seconds, 30 seconds, etc. Optionally, the first preset duration can also be set by the user. In this example, the first preset duration is 20 seconds.

[0184] Step 1007: When the display module detects the first preset event, it resets the time.

[0185] Specifically, within a first preset duration, if the display module detects a first preset event, the timer is instructed to restart. The first preset event can be a preset touch operation, such as clicking the screen, sliding on the screen (such as a quick slide, an up-slide operation, a down-slide operation, etc.), a drag operation, etc. The first preset event can also be an event of human eyes looking at the screen. The mobile phone is provided with a human eye gaze detection module. The human eye gaze detection module can identify the human eye iris and determine whether a human eye is looking at the screen based on the distance between the human eye iris and the screen and whether the distance between the human eye and the screen is decreasing. For example, when the human eye gaze detection module detects that the distance between the human eye iris and the screen of the mobile phone is less than 80 cm and the distance between the human eye and the screen is decreasing, it is determined that there is an event of human eyes looking at the screen. The human eye gaze detection module can record the detection result, for example, using "eye_event=true" to indicate that there is an event of human eyes looking at the screen. The display module can monitor the recorded human eye gaze result, and when it detects that the human eye gaze result indicates that there is an event of human eyes looking at the screen, it instructs the timer to restart the timing of 20 seconds.

[0186] Optionally, within the first preset time period, if the display module detects a first preset event, the timing threshold of this timer can be adjusted to extend the time period for the display screen to display the target service interface. For example, the display module instructs to update the timing threshold of this timer from the first preset time period (such as 20 seconds) to the second preset time period (such as 25 seconds).

[0187] Step 1008: When the timer reaches the timing threshold, a prompt message is sent to the display module.

[0188] Specifically, when the timer reaches the timing threshold set this time (such as 20 seconds), a prompt message can be sent to the display module.

[0189] Step 1009: The display module receives a prompt message indicating that the timer has reached a predetermined duration, and instructs the status management module to set the screen off, and the status management module performs the screen off operation.

[0190] Specifically, when the display module receives the timer prompt information, it indicates that the display module has not received the first preset event within the first preset time period. To reduce the power consumption of the mobile phone, the display module can instruct the status management module to set the screen off after receiving the timer prompt information. After receiving the instruction, the status management module performs the screen off operation.

[0191] Step 1010: After the mobile phone turns off the screen, the display module monitors a first preset event.

[0192] Specifically, after the mobile phone turns off the screen, the display module can monitor the first preset event and light up the screen in time.

[0193] Step 1011: When the display module detects a first preset event, it instructs the status management module to light up the screen.

[0194] Specifically, the status management module lights up the display screen according to the instruction.

[0195] Step 1012: After the screen is re-lit, the display module instructs the timer to restart timing.

[0196] Specifically, the display module lights up the display screen again so that the user can continue to view the target image, and at the same time, instructs the timer to reset to 20 seconds.

[0197] In some embodiments, FIG10 specifically illustrates different display strategies of the smart display stand. When the mobile phone is in charging state and the switch in the smart display stand is turned on, the display screen is controlled to always display the target service interface during the charging period.

[0198] When the mobile phone is not in charging state or the switch in the smart display stand is not turned on, there are three display strategies. When the mobile phone is not in charging state or the switch in the smart display stand is not turned on, the display screen starts to display the target service interface and instructs the timer to start the 20-second timing. At the end of the 20-second timing, when the display module does not detect the first preset event, the status management module is instructed to perform the screen-off operation. During the 20-second timing process, when the first preset event is detected, the timer is instructed to restart the 20-second timing or extend the timing. After the status management module controls the display screen to turn off, if the first preset event is detected, the status management module can be instructed to re-light the display screen and the timer can be instructed to restart timing.

[0199] It should be noted that when the mobile phone is running the smart display, when the power manager detects that the display screen has switched to the bright screen state, the power manager exits the Doze state and ends the operation of the smart display. The bright screen state is the state of the screen when the mobile phone is running normally after being unlocked.

[0200] The following describes in detail the process of displaying the target service interface of the smart table in different scenarios with reference to the accompanying drawings.

[0201] Assume that the following scenarios all meet the conditions for starting the smart display.

[0202] Scenario 1:

[0203] Assume that the permanent display switch of the smart display stand is turned on and the mobile phone is in a charging state. As shown in 11a in Figure 11, the mobile phone is connected to the charging cable 1102. When the display module has detected that the permanent display switch in the smart display stand is turned on and that the mobile phone is in a charging state, it can instruct the display screen 1101 to display the target service interface (the target service interface is a calendar). The mobile phone is in a charging state between 9:00 and 9:20, and the state of the permanent display switch has not changed. During the period from 9:00 to 9:20, as shown in 11b in Figure 11, the display screen 1103 of the mobile phone always displays the calendar interface.

[0204] Scenario 2:

[0205] Assuming the phone is not charging and the target image is a calendar, as shown in 12a of Figure 12 , upon detecting that the phone is not charging, the display 1201 of the phone begins displaying the target service interface. When the display begins displaying the target service interface, the display module instructs a timer to start for 20 seconds.

[0206] If the display module detects no touch operation or eye contact within 20 seconds after the timer starts, the display module instructs the status management module to turn off the display screen. As shown in 12b of Figure 12, the display screen 1202 is in the screen-off state. It should be noted that in the screen-off state, the mobile phone does not exit the smart display; only the display screen is turned off.

[0207] Scenario 3:

[0208] As shown in 13a in Figure 13, the mobile phone is connected to the charging cable 1302. When the display module has detected that the always-on display switch in the smart display stand is turned on and that the mobile phone is in a charging state, it can instruct the display screen 1301 to display the target service interface. When the user disconnects the charging cable 1302 from the mobile phone, the display screen 1303 of the mobile phone switches to a bright screen state, as shown in 13b in Figure 13. When the power manager of the mobile phone detects that the display screen has switched to a bright screen state, the power manager controls the mobile phone to exit the Doze state, thereby causing the mobile phone to exit the smart display stand. After the display screen of the mobile phone switches to a bright screen state, if the mobile phone does not receive a touch operation from the user within a third preset time length (such as 10 seconds, 30 seconds, etc.), the mobile phone performs a screen-off operation. As shown in 13c in Figure 13, the display screen 1304 of the mobile phone is in a screen-off state.

[0209] When the power manager detects that the display has switched to the off state, it retrieves the status value from the database. If the power manager detects that the current phone meets the conditions for activating the smart display, it activates the smart display. The smart display detects that the current phone is not charging, and as shown in 13d in Figure 13, the display 1305 begins displaying the target service interface and starts a 20-second timer.

[0210] Scenario 4:

[0211] As shown in 14a in Figure 14, when the display module has detected that the mobile phone is not in a charging state, it can instruct the display screen 1401 to display the target service interface and start a 20-second timer. When the timer counts to 15 seconds, if the user connects the mobile phone to the charging cable 1403, the display screen 1402 of the mobile phone is switched to a bright screen state to display a charging prompt image, as shown in 14b in Figure 14. When the power manager of the mobile phone detects that the display screen has switched to a bright screen state, the power manager controls the mobile phone to exit the Doze state, thereby causing the mobile phone to exit the smart display. After the display screen of the mobile phone is switched to a bright screen state, if the mobile phone does not receive a touch operation from the user within a third preset time length (such as 10 seconds, 30 seconds, etc.), the mobile phone performs a screen-off operation. As shown in 14c in Figure 14, the display screen 1405 of the mobile phone is in a screen-off state.

[0212] When the power manager detects that the display has switched to the off state, it retrieves the status value from the database. If the power manager detects that the current phone meets the conditions for activating the smart display, it activates the smart display. The smart display detects that the current phone is not charging, and as shown in 14d in Figure 14, the display 1404 begins displaying the target service interface and starts a 20-second timer.

[0213] Scene 5:

[0214] As shown in 15a in Figure 15, when the display module has detected that the mobile phone is not in a charging state, it can instruct the display screen 1501 to display the target service interface and start the 20-second timer. When the timer counts to 15 seconds (that is, when the 20-second count has not ended), if the mobile phone receives an incoming call request, the display screen 1502 of the mobile phone switches to a bright screen state to display the call interface, as shown in 15b in Figure 15. When the power manager of the mobile phone detects that the display screen has switched to a bright screen state, the power manager controls the mobile phone to exit the Doze state, thereby causing the mobile phone to exit the smart display. After the user ends the call, if the mobile phone does not receive a touch operation from the user within a third preset time length (such as 10 seconds, 30 seconds, etc.), the mobile phone performs a screen-off operation. As shown in 15c in Figure 15, the display screen 1503 of the mobile phone is in a screen-off state.

[0215] When the power manager detects that the display has switched to the off state, it retrieves the status value from the database. If the power manager detects that the current phone meets the conditions for activating the smart display, it activates the smart display. The smart display detects that the current phone is not charging, and as shown in 15d in Figure 15, the display 1504 begins displaying the target service interface and starts a 20-second timer.

[0216] Scene 6:

[0217] As shown in 16a in FIG16 , when the display module has detected that the mobile phone is not in a charging state, it can instruct the display screen 1601 to display the target service interface (such as the picture in the gallery) and start the 20-second timer. When the timer reaches 10 seconds (i.e., before the 20-second timer ends), the mobile phone responds to the user's left swipe operation (as shown in 16c in FIG16 , the user's finger slides along the black arrow on the display screen 1602) and displays the next picture in the gallery on the display screen (as shown in 16c in FIG16 , the display screen 1603 displays the next image), and the timer is reset to 20 seconds.

[0218] Scene 7:

[0219] As shown in 17a of Figure 17, when the display module detects that the mobile phone is not in a charging state, it can instruct the display screen 1701 to display the target service interface (such as the interface in the calendar) and start the 20-second timer. During the 20-second timer, if the smart display does not detect the first preset event, the screen is turned off (as shown in 17b of Figure 17). In response to the user's operation of clicking the display screen 1702, the smart display re-lights the display screen 1703 and restarts the 20-second timer (as shown in 17c of Figure 17).

[0220] Scene 8:

[0221] As shown in 18a in Figure 18, when the display module has detected that the mobile phone is not in a charging state, it can instruct the display screen 1801 to display the target service interface (such as the interface in the calendar) and start the 20-second timer. During the 20-second timer, if the user switches the screen from the stand state to the vertical screen state, the System Server monitors that the mobile phone is not in the stand state and updates the status value in the database from "1" to "0". The smart display detects that the status value is updated from "1" to "0" and controls the display screen to switch to the bright screen state (as shown in 18b in Figure 18, the display screen 1802 is in the bright screen and locked screen state). When the power manager detects that the display screen has switched to the bright screen state, it controls the mobile phone to exit the Doze state, that is, exit the smart display.

[0222] It is understandable that when the user switches the mobile phone from the stand state to the non-stand state (such as the portrait state), the mobile phone can exit the smart display. This method does not require the user to perform any click operations to exit the smart display, reducing the user's operations and improving the user experience.

[0223] Currently, electronic devices have a variety of display applications in low-power states, such as the smart display stand and off-screen display in this application. The startup and exit of the smart display stand can refer to the relevant descriptions in Figures 3 to 5. The off-screen display (application) includes two services, namely the global AOD service (ie, the first service) and the local AOD service (the second service). Users can select the service form (ie, mode) of the off-screen display according to display needs. Figure 19 is an exemplary setting interface for the off-screen display. As shown in Figure 19, the off-screen display interface 1901 includes an option 1902 for allowing or prohibiting the electronic device from starting the off-screen display; in response to the user turning on the switch 19021 in option 1902, the mobile phone allows the electronic device to start the off-screen display when the conditions for starting the off-screen display are met. The interface 1901 also includes an off-screen mode selection item 1903; the off-screen mode selection item 1903 includes a display style 19031 for the global AOD, and a display style 19032 for the local AOD. The user can select the screen-off mode as needed. As shown in FIG19 , in response to the user clicking on the display style 19031 , the mobile phone can record the identification information of the global AOD to indicate that the screen-off display mode is the global AOD.

[0224] It should be noted that when the screen is off and the display mode of the global AOD is adopted, the mobile phone is in the lock screen and the brightness of the display is dimmed. The wallpaper displayed in the global AOD mode can be selected by the user. When the mobile phone is in global AOD mode, the mobile phone can allow images of other applications (also called layers), such as notifications, navigation bars and other interfaces, to be displayed while displaying the wallpaper of the global AOD. When the mobile phone is in local AOD mode, the mobile phone displays images in a preset area when the screen is locked, such as the display style of 19032 in Figure 19. When the mobile phone is in local AOD mode, the mobile phone does not allow images of other applications to be displayed on the display.

[0225] When the mobile phone starts the smart display, while the smart display is preparing the target service interface, images of other applications are sent to the display screen before the target service interface of the smart display. The display screen will display the images of other applications first. When the display screen receives the target service interface, it covers the images of other applications and displays the target service interface. This causes the display screen to flicker when running the smart display. The process of preparing the target service interface of the smart display includes the application sending the drawn image to the window manager, which draws the image; and transmitting the drawn image to SurfaceFlinger, which renders the image and sends the rendered image to the display screen.

[0226] Figure 20 is a schematic diagram of a scene showing a flash screen. As shown in Figure 20, the 20a interface, 20b interface, 20c interface, 20d interface, 20e interface and 20f interface in Figure 20 form a continuous screen, 20a interface is the first frame, 20b interface is the second frame, 20c interface is the third frame, 20d interface is the fourth frame, 20e interface is the fifth frame, and 20f interface is the sixth frame. The first to second frames are the lock screen interfaces of the mobile phone, and the fourth to sixth frames should all be the calendar interfaces of the smart table application (i.e., the target service interface), but a notification appears in the third frame, i.e., the 20c interface. This causes the smart table to flash when displaying the target service interface, affecting the user's use of the mobile phone.

[0227] An embodiment of the present application also provides a display method, when an electronic device starts a smart display, the display status of the electronic device and a fourth indication information are sent to an image synthesizer (SurfaceFlinger), and the display status is used to indicate the display mode of the electronic device in a low-power state. The display modes in the low-power state include: smart display, global AOD, and local AOD. The fourth indication information can indicate whether SurfaceFlinger adopts a strategy for filtering out images of other applications. For example, the fourth indication information can be "0", and the "0" is used to indicate the strategy for filtering out images of other applications. If the fourth indication information is "1", it is used to indicate that the strategy for filtering out images of other applications is not adopted. SurfaceFlinger adopts a display strategy corresponding to the current display state according to the display state to filter out images that are not allowed to be displayed in the current display state. After the mobile phone exits the current display state, SurfaceFlinger cancels the display strategy corresponding to the display state.

[0228] In this example, SurfaceFlinger in the electronic device filters out images that are not allowed to be displayed based on the current display status. This can avoid the screen flickering problem caused by the display showing images of other applications while the smart display or local AOD is preparing the image, and can also solve the coupling problem between the AOD and the smart display.

[0229] The following specifically describes the process of filtering images of other applications in the smart table setting mode in this application with reference to FIG21. In this example, a mobile phone is used as an example of an electronic device.

[0230] Step 2101: The system service detects that the conditions for starting the smart display are met.

[0231] This step is similar to step 603. Please refer to the relevant description in step 603 and will not be repeated here.

[0232] Step 2102: After receiving the system's instruction for the service, the power manager starts Standby.

[0233] This step is similar to step 604 , and the relevant description in step 604 may be referred to, which will not be repeated here.

[0234] Step 2103: The smart display sends the current status to SurfaceFlinger.

[0235] Specifically, since the smart display provides three low-power modes, namely, smart display mode, global AOD mode, and local AOD mode, when the power manager activates Standby, the smart display can record the identification information of the low-power mode currently entered by the mobile phone. For example, in this example, when the power manager activates Standby, the smart display records the identification information of the Standby, which can be the package name of the Standby.

[0236] During the startup of the smart display, the smart display can send fourth indication information and identification information of the smart display to SurfaceFlinger. The fourth indication information is used to instruct SurfaceFlinger to adopt a strategy of filtering out images not sent by the smart display. In this example, the fourth indication information can be identified by "0".

[0237] Step 2104: SurfaceFlinger obtains the display policy for entering the Standby state.

[0238] Specifically, after SurfaceFlinger obtains the Standby package name, it determines, based on the fourth indication information, to adopt a display strategy that filters out images not sent by the smart display. This display strategy corresponds to a preset whitelist. The display strategy corresponding to Standby can be to allow layers on the Standby whitelist to be displayed.

[0239] Standby can obtain the target service interface and add an image tag to it. This image tag indicates the application that drew the image. For example, if the target service interface is a calendar interface, Standby obtains the calendar interface and adds the Standby package name as the image tag. Standby sends the drawn image to the window manager, which draws the image and transfers it to SurfaceFlinger for rendering.

[0240] In this example, when the window manager transmits the drawn image to SurfaceFlinger, SurfaceFlinger can determine whether to transmit the image to the display screen according to the determined display policy.

[0241] In one example, the electronic device can pre-store the display policy corresponding to each mode in low power mode (such as smart display, first service, and second service). The electronic device can pre-set a whitelist of interfaces allowed to be displayed for each mode, and the whitelist can store the package name of Standby.

[0242] For example, SurfaceFlinger obtains the display policy corresponding to Standby. The display policy includes: a whitelist of interfaces allowed to be displayed in the Standby mode. After receiving the image sent by the window manager, SurfaceFlinger can detect whether the image tag of the image is the same as the identification information stored in the Standby whitelist. If it is detected that the image belongs to the image in the whitelist, the image is allowed to be displayed. SurfaceFlinger can render the image and send the image to the display screen through the window manager. If it is detected that the image does not belong to the whitelist, the image is not allowed to be displayed, that is, the currently received image is filtered out.

[0243] Optionally, SurfaceFlinger can add Standby's identification information to the whitelist, where the Standby's identification information can be the Standby package name.

[0244] For example, after the SurfaceFlinger obtains the package name of the Standby, it adds the package name of the Standby to the whitelist. SurfaceFlinger obtains the display policy corresponding to Standby. The display policy includes: displaying layers that belong to the Standby whitelist. After receiving the interface sent by the window manager, SurfaceFlinger can detect whether the interface belongs to a layer in the whitelist based on the image tag in the interface. If a layer in the whitelist is detected, the interface is allowed to be displayed, the received image can be rendered, and the image is sent to the display screen through the window manager. If a layer that does not belong to the whitelist is detected, the layer is not allowed to be displayed, that is, the currently received layer is filtered out.

[0245] Step 2105: The smart table instructs the window manager to initialize the Standby interface.

[0246] Specifically, the smart stand transmits the acquired target service interface to the window manager, and the window manager draws the interface sent by Standby.

[0247] Step 2106: The window manager draws the Standby interface.

[0248] Specifically, the window manager draws the Standby interface according to the instructions of the smart display.

[0249] Step 2107: The window manager sends the drawn interface to SurfaceFlinger.

[0250] Specifically, after SurfaceFlinger receives the interface sent by Standby transmitted by the window manager, it can detect whether the interface belongs to a layer in the whitelist. If it is detected that it belongs to a layer in the whitelist, the interface is allowed to be displayed and the received image can be rendered.

[0251] If a layer that does not belong to the whitelist is detected, the layer will not be allowed to be displayed, that is, the currently received layer will be filtered out.

[0252] Step 2108: The power manager switches to Doze state.

[0253] Specifically, after the power manager completes pulling up Standby, the power manager instructs the smart display to switch to Doze state, that is, the mobile phone starts running in Doze state, so that the display screen displays the Standby interface when the mobile phone is in a low power consumption state.

[0254] It should be noted that after the power manager completes pulling up the Standby, the Standby can register with the database to monitor changes in the status value of the mobile phone stored in the database.

[0255] Step 2109: The smart display instructs the power manager to light up the display screen.

[0256] Specifically, after the smart display unit switches to the Doze state, the smart display unit instructs the power manager to light up the display screen, that is, to light up the backlight of the display screen.

[0257] Step 2110: The backlight of the display turns on and the Standby interface is displayed.

[0258] Specifically, after the backlight of the display is turned on, the display obtains the Standby interface rendered by SurfaceFlinger through the window manager.

[0259] Step 2111: When the electronic device exits the stand state, the system service instructs the smart display electronic device to exit the stand state.

[0260] Specifically, when the electronic device exits the stand state, the system service detects that the mobile phone does not meet the conditions for starting the smart display, and updates the status value in the database from the first value to the second value. When the smart display detects that the status value in the database changes from the first value to the second value, it can instruct the power manager to control the display to switch to the bright screen state, that is, execute step 2112. In this example, the bright screen state refers to the state in which the mobile phone display is displaying the interface in normal mode.

[0261] Step 2112: The smart display instructs the power manager to set the screen to bright according to the instructions of the system service.

[0262] Step 2113: The power manager controls the display screen to switch to a bright screen state.

[0263] Step 2114: When the power manager detects that the display screen has switched to the bright screen state, the smart display operation ends.

[0264] Specifically, when the power manager detects that the display screen is in the bright screen state, it exits the Doze state, that is, exits the DreamService of Standby. The power manager exits the DreamService of Standby, that is, controls the smart display to stop running.

[0265] Step 2115: The smart display sends the status of exiting Standby to SurfaceFlinger.

[0266] Specifically, when the smart display device ends its operation, the device can obtain the setting information of whether the mobile phone is allowed to run the screen-off display. For example, when the user turns on the switch 19021 shown in Figure 19 and the user selects the screen-off mode, the electronic device can store the setting information, which can indicate whether the electronic device is allowed to run the screen-off display and whether the running mode is global mode or local mode.

[0267] When the smart display detects that the electronic device allows global AOD to run and determines that SurfaceFlinger does not adopt the display strategy of filtering out layers sent by other applications, it can send a fifth indication message to SurfaceFlinger. The fifth indication message instructs SurfaceFlinger to adopt the second display strategy, that is, SurfaceFlinger transmits the received image to the display screen, that is, SurfaceFlinger does not perform the image filtering operation.

[0268] When the smart display detects that the electronic device allows the local AOD to run and determines that SurfaceFlinger adopts the third display strategy, it can send a fifth indication message to SurfaceFlinger. The fifth indication message instructs SurfaceFlinger to adopt the third display strategy, that is, SurfaceFlinger transmits the image sent by the local AOD to the display screen and filters out the image not sent by the local AOD.

[0269] When the smart display detects that the electronic device is not allowed to run with the screen off, and determines that SurfaceFlinger adopts the fourth display strategy, it can send a fifth indication message to SurfaceFlinger. The fifth indication message instructs SurfaceFlinger to adopt the fourth display strategy, that is, SurfaceFlinger filters out the received image, that is, ensures that the electronic device is in the screen off state.

[0270] Step 2116: SurfaceFlinger obtains the display policy for exiting the Standby state.

[0271] Specifically, SurfaceFlinger obtains the current display policy according to the fifth indication information, that is, cancels the display policy of filtering out images that are not sent by Standby.

[0272] After SurfaceFlinger receives the image sent by the window manager, it can determine whether to send the image to the display screen according to the current display policy. When SurfaceFlinger determines to adopt the second display policy, SurfaceFlinger transmits the received image to the display screen, that is, SurfaceFlinger does not perform image filtering. When SurfaceFlinger determines to adopt the third display policy, SurfaceFlinger transmits the image sent by the local AOD to the display screen and filters out images that are not sent by the local AOD. When SurfaceFlinger determines to adopt the fourth display policy, SurfaceFlinger filters the received image.

[0273] It should be noted that when the mobile phone is running the smart display, when the power manager detects that the display screen has switched to the bright screen state, the power manager exits the Doze state and ends the operation of the smart display. Among them, the bright screen state is the state of the screen when the mobile phone is running normally after being unlocked.

[0274] FIG. 22 exemplarily shows a process in which an electronic device determines a display strategy.

[0275] Step 2201: The mobile phone starts Standby.

[0276] The description of this process can be found in steps 2101 and 2102 and will not be repeated here.

[0277] Step 2202: The smart display sends instruction information to SurfaceFlinger.

[0278] The description of this process can be found in the description of step 2103 and will not be repeated here.

[0279] Step 2203: SurfaceFlinger obtains the corresponding display strategy based on the status information.

[0280] The description of this process can be found in the description of step 2104 and will not be repeated here.

[0281] Step 2204: The power manager ends the Standby operation.

[0282] The description of this process can be found in steps 2111 to 2112 and will not be repeated here.

[0283] Step 2205: After the smart display detects that Standby has ended, it determines whether the current mobile phone is in the global AOD state. If so, execute step 2206; if not, execute 2202.

[0284] Specifically, after the smart display detects that Standby has ended, the smart display can obtain the setting information of the electronic device. When the setting information indicates that the electronic device is running a partial AOD or has disabled the off-screen display application, the smart display executes step 2202, i.e., the smart display generates fifth indication information based on the setting information and sends the fifth indication information to SurfaceFlinger. For the specific process, please refer to the relevant description in step 2115.

[0285] Optionally, the SurfaceFlinger may directly obtain the current display strategy according to the fifth indication information, and determine whether to transmit the received image to the display screen according to the determined display strategy.

[0286] When the electronic device runs a local AOD, SurfaceFlinger determines to adopt the third display strategy. When SurfaceFlinger receives an image, it transmits the image sent by the local AOD to the display screen and filters out the image not sent by the AOD.

[0287] When the electronic device is in the screen-off state, SurfaceFlinger determines to adopt the fourth display strategy, and SurfaceFlinger filters the received image when receiving the image.

[0288] Step 2206: SurfaceFlinger cancels layer filtering.

[0289] Specifically, when the electronic device runs all AODs, SurfaceFlinger determines to adopt the second display strategy, that is, SurfaceFlinger transmits the received image to the display screen, that is, SurfaceFlinger does not perform an image filtering operation.

[0290] FIG23 exemplarily shows a schematic diagram of layers displayed on the display screen when the mobile phone is in the Standby state.

[0291] As shown in 23a of Figure 23, assuming that the mobile phone is in Standby mode and the display method in this application is not used, a schematic diagram of the layers of the display screen is shown. As shown in 23a, after the mobile phone starts the smart display, the smart display is preparing the target service interface. The images of other applications are sent to the display screen before the target service interface of the smart display. The display screen will first display the images of other applications (such as the left-hand gesture navigation bar and the right-hand gesture navigation bar). When the display screen receives the Standby interface, it displays the Standby interface.

[0292] As shown in 23b of Figure 23, assuming that the phone is in Standby mode and the display method described in this application is used, after the phone starts the smart display, while the smart display is preparing the target service interface, SurfaceFlinger detects that the image of other applications is not in the Standby whitelist and does not allow the layer to be displayed.

[0293] Figure 24 is a schematic diagram illustrating a scenario using the display method described in this application. As shown in Figure 24, interfaces 24a, 24b, 24c, 24d, 24e, and 24f in Figure 24 form a continuous screen, with interface 24a being the first frame, interface 24b being the second frame, interface 24c being the third frame, interface 24d being the fourth frame, interface 24e being the fifth frame, and interface 24f being the sixth frame. The first to second frames are the phone lock screen interfaces, and the third to sixth frames should all be the calendar interfaces (i.e., the target service interfaces) of the smart table setting application, and no more screen flickering should occur.

[0294] It is understandable that, in order to implement the above functions, the electronic device includes hardware and / or software modules that perform the corresponding functions. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of this application.

[0295] An embodiment of the present application further provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (such as a memory of an electronic device). For another example, the interface circuit can be used to send signals to other devices (such as a processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform the various steps in the above embodiments. Of course, the chip system can also include other discrete devices, which is not specifically limited in the embodiment of the present application.

[0296] This embodiment further provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes the above-described related method steps to implement the display method described in the above embodiment. The storage medium includes various media capable of storing program code, such as a USB flash drive, a mobile hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0297] This embodiment further provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement the display method in the above-mentioned embodiment.

[0298] Among them, the electronic device, computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding display method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0299] Any content of each embodiment of this application, as well as any content of the same embodiment, can be freely combined. Any combination of the above content is within the scope of this application.

[0300] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A display method, characterized in that, Applied to an electronic device, where a first application is installed in the electronic device, and the first application inherits from a low-power mode; the method includes: When the electronic device is in the docked state, start the first application; The first application determines a target service interface to be displayed on the display screen by the first application this time according to the service interface displayed on the display screen controlled by the first application last time. The service interface adopted when the first application runs for the first time is determined by a service interface recommendation model; When it is detected that the electronic device is in a charging state, the first application controls the display screen to display the target service interface during the charging period of the electronic device; When it is detected that the electronic device is not in a charging state, the first application controls the display screen to display the target service interface within a first preset duration.

2. The method according to claim 1, wherein The first application includes: a state management module, a display module, and a timer; When it is detected that the electronic device is not in a charging state, the first application controls the display screen to display the target service interface within a first preset duration, including: When the display module detects that the electronic device is not in a charging state, it controls the display screen to display the target service interface and starts the timer; When the display module detects that the timer reaches the first preset duration, it transmits first indication information to the state management module; The state management module sets the display screen to switch to the screen-off state according to the first indication information.

3. The method according to claim 2, wherein After the display screen switches to the screen-off state, the method further includes: When the display module detects a first preset event, it transmits second indication information to the state management module. The first preset event includes a preset touch operation or an event that a human eye gazes at the display screen; The state management module sets the display screen to light up the screen according to the second indication information; The display module instructs the timer to restart timing.

4. The method according to claim 2, characterized in that, The method further includes: Within the first preset duration, when the display module detects a first preset event, it instructs the timer to restart timing. The first preset event includes a preset touch operation or an event that a human eye gazes at the display screen.

5. The method according to claim 2, wherein The method further includes: Within the first preset duration, when the display module detects a first preset event, it increases the timing threshold of the timer this time by a second preset duration. The first preset event includes a preset touch operation or an event that a human eye gazes at the display screen.

6. The method according to claim 2, wherein The electronic device includes a power manager; the method further includes: When the power manager detects that the electronic device switches to the screen-on state, it controls the first application to end running. The brightness of the display screen when it is in the screen-on state is greater than the brightness of the display screen when the first application controls the display screen to display the target service interface.

7. The method according to claim 6, wherein The method further includes: In response to an operation of connecting the electronic device to a charger or an operation of disconnecting the electronic device from the charger, the electronic device switches to the screen-on state.

8. The method according to claim 6, wherein The method further includes: In response to an operation of pressing a power button input by a user, the electronic device switches to the screen-on state.

9. The method according to claim 2, wherein When it is detected that the electronic device is in a charging state, before the first application controls the display screen to display the target service interface during the charging period of the electronic device, the method includes: The display module detects whether a first service function in the first application is enabled, and the first service function is used to indicate that the electronic device allows the first application to control the display screen to display the target service interface during the charging period; The display module detects that the first service function has been enabled.

10. The method according to any one of claims 1-9, characterized in that, Before starting the first application, the method further includes: When the system service of the electronic device detects that the electronic device is in a docked state, the system service detects whether a status value of the electronic device is a first value, and the status value is used to indicate whether the electronic device meets the condition for allowing the first application to be started; When the system service detects that the status value is the first value, it transmits third indication information to the power manager of the electronic device to instruct the power manager to start the first application; Starting the first application includes: The power manager starts the first application according to the third indication information.

11. The method according to claim 10, wherein The method further includes: Registering the system service when the electronic device is powered on; The system service monitors the status of each item to be monitored; The system service determines the status value of the electronic device according to the status of each item to be monitored and stores the status value.

12. The method according to claim 11, wherein Starting the first application includes: When the power manager detects that the electronic device switches to the screen-off state, it detects whether the status value of the electronic device is the first value; When the power manager detects that the status value of the electronic device is the first value, it starts the first application.

13. The method according to claim 11, wherein The method further includes: The system service obtains preset monitoring items; The system service obtains service items supported by the electronic device; The system service obtains the intersecting items between the preset monitoring items and the service items supported by the electronic device, and uses the intersecting items as the items to be monitored.

14. The method according to claim 13, wherein The preset monitoring items include: whether the account logged in to the electronic device is the account of the main user, whether the electronic device allows the first application to run, whether the electronic device has turned off the privacy moment service, whether the electronic device is in a docked state, whether the electronic device is in an unlocked state, whether the electronic device is not in a call state, whether the electronic device is not remotely locked, whether the electronic device is not in the state of the startup wizard, whether the electronic device is not in the holster mode, whether the electronic device is not in the virtual reality VR mode, and whether the electronic device is not in the power-saving mode.

15. The method according to claim 14, wherein If the service items supported by the electronic device include the preset monitoring items; The system service determines the status value of the electronic device according to the status of each item to be monitored, including: When the system service detects that the account logged in to the electronic device is the account of the primary user, the electronic device allows the first application to run, the electronic device turns off the privacy moment service, the electronic device is in the docked state, the electronic device is in the unlocked state, the electronic device is not in a call state, the electronic device is not remotely locked, the electronic device is not in the state of the startup wizard, the electronic device is not in the holster mode, the electronic device is not in the VR mode, and the electronic device is not in the power saving mode, determine that the status value of the electronic device is the first numerical value.

16. The method according to claim 1, characterized in that When the display module detects that the electronic device is not in the charging state, it controls the display screen to display the target service interface, including: When the first application starts, it sends the first information of the electronic device to the image synthesizer of the electronic device. The first information includes the fourth indication information and the first identification information of the first application. The fourth indication information is used to instruct the image synthesizer to obtain the first display strategy. The image synthesizer determines that the image synthesizer adopts the first display strategy according to the first information. When the image synthesizer receives the first image to be displayed, it detects whether the first image belongs to the image sent by the first application according to the first display strategy. When the image synthesizer detects that the first image belongs to the image sent by the first application, it transmits the first image to the display screen, and the display screen displays the first image. When the image synthesizer detects that the first image does not belong to the image sent by the first application, it filters out the first image.

17. The method according to claim 16, wherein The image synthesizer determines that the image synthesizer adopts the first display strategy according to the first information, including: The image synthesizer obtains the first preset list according to the fourth indication information. The image synthesizer adds the first identification information to the first preset list. The first display strategy is used to indicate that the image synthesizer allows the image belonging to the first preset list to be transmitted to the display screen.

18. The method according to claim 17, wherein The image synthesizer detects whether the first image belongs to the image sent by the first application according to the first display strategy, including: The image synthesizer obtains the image label of the first image as the first label, and the first label is the identification information of the application that generates the first image. The image synthesizer detects whether there is the same identification information as the first label in the first preset list. When the image synthesizer detects that there is the same identification information as the first label in the first preset list, it determines that the first image belongs to the image sent by the first application. When the image synthesizer detects that there is no same identification information as the first label in the first preset list, it determines that the first image does not belong to the image sent by the first application.

19. The method according to claim 17, wherein The method further includes: When the first application ends running, it obtains the setting information of the electronic device. The setting information is used to indicate the information of the service that the electronic device allows to start in the low power consumption state. The first application sends fifth indication information to the image synthesizer according to the setting information; The image synthesizer obtains the display strategy adopted by the image synthesizer according to the fifth indication information; When receiving the second image, the image synthesizer determines whether to transmit the second image to the display screen according to the currently determined display strategy.

20. The method according to claim 19, wherein The first application sending fifth indication information to the image synthesizer according to the setting information includes: When the first application detects that the service allowed to run by the electronic device in the low-power state indicated by the setting information is the first service, generate the fifth indication information; the fifth indication information instructs the image synthesizer to adopt a second display strategy, and the second display strategy is used to instruct the image synthesizer to send the received image to the display screen; When receiving the second image, the image synthesizer determining whether to transmit the second image to the display screen according to the currently determined display strategy includes: When receiving the second image, the image synthesizer sends the second image to the display screen according to the indication of the second display strategy.

21. The method according to claim 19, wherein The first application sending fifth indication information to the image synthesizer according to the setting information includes: When the first application detects that the service allowed to be started by the electronic device in the low-power state indicated by the setting information is the second service, generate the fifth indication information; the fifth indication information instructs the image synthesizer to adopt a third display strategy, and the third display strategy instructs the image synthesizer to allow the image sent by the second service to be transmitted to the display screen; When receiving the second image, the image synthesizer determining whether to transmit the second image to the display screen according to the currently determined display strategy includes: When receiving the second image, the image synthesizer detects whether the second image belongs to the image sent by the second service according to the third display strategy; When the image synthesizer detects that the second image belongs to the image sent by the second service, transmit the second image to the display screen, and the display screen displays the second image; When the image synthesizer detects that the second image does not belong to the image sent by the second service, filter the second image.

22. The method according to claim 19, wherein The first application sending fifth indication information to the image synthesizer according to the setting information includes: When the first application detects that the setting information indicates that the electronic device runs the screen-off service in the low-power state, generate the fifth indication information, and the fifth indication information instructs the image synthesizer to adopt a fourth display strategy, and the fourth display strategy instructs the image synthesizer to prohibit transmitting the received image to the display screen; When receiving the second image, the image synthesizer determining whether to transmit the second image to the display screen according to the currently determined display strategy includes: When receiving the second image, the image synthesizer filters the second image according to the indication of the fourth display strategy.

23. The method according to claim 19, wherein The services that the electronic device allows to start in the low-power state include a first service, a second service, and a screen-off service; When the first service is started, the first service controls the display screen to display a first preset image when the electronic device is in the locked screen state, and the brightness of the display screen when displaying the first preset image is less than a first brightness, and the first brightness is the brightness of the display screen when the electronic device is in the normal operation state; When the second service is started, the second service controls to display a second preset image in a first area of the display screen when the electronic device is in the locked screen state, the first display area is smaller than the area of the display screen, and the brightness of the display screen when displaying the second preset image is less than the first brightness.

24. A chip system, characterized in that, It includes a processor for calling and running a computer program from a memory, so that the electronic device installed with the chip system executes the display method described in any one of claims 1 to 23.

25. An electronic device, characterized in that, It includes: A memory and a processor, the memory is coupled to the processor; The memory stores program instructions, and when the program instructions are executed by the processor, the electronic device executes the display method described in any one of claims 1 to 23.

26. A computer-readable storage medium, comprising a computer program, characterized in that, When the computer program runs on the electronic device, the electronic device executes the display method described in any one of claims 1 to 23.

Images