Display method and apparatus

Abstract

Embodiments of the present application relate to the technical field of terminals, and provide a desktop display method and apparatus. The method comprises: when a terminal device detects a combined scenario, such as a scenario in which the terminal device displays a desktop, enters a setting application for screen rotation and wallpaper setting, and exits a desktop application, the terminal device can actively acquire information on configuration change upon determination that no information on configuration change sent by another module is received, so that the desktop application can adaptively adjust the desktop layout on the basis of the direction of screen rotation, thereby reducing layout abnormalities.

Description

Display method and device Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a desktop display method and device. Background Art

[0002] With the popularization and development of the Internet, people's functional requirements for terminal devices are becoming more and more diverse. For example, in order to meet users' usage habits of terminal devices, terminal devices can support users' screen rotation, wallpaper setting and other functions.

[0003] However, when the terminal device displays the desktop, when the terminal device rotates the screen and sets the wallpaper in the setting application based on the user operation and then returns to the desktop application, the desktop application may have an abnormal layout.

[0004] Summary of the Invention

[0005] An embodiment of the present application provides a desktop display method and apparatus. When a terminal device detects a combined scenario, such as displaying the desktop, entering a settings application to rotate the screen, setting a wallpaper, and exiting a desktop application, the terminal device can proactively initiate configuration change information so that the desktop layout can be adaptively adjusted according to the direction of screen rotation, thereby reducing layout anomalies.

[0006] In a first aspect, an embodiment of the present application provides a desktop display method, which is applied to a terminal device, and the method includes: at a first time point, displaying a first interface, the first interface is a desktop, and the wallpaper of the first interface is a first image; at a second time point, displaying a second interface, the second interface includes a thumbnail of the second image, the second time point is later than the first time point, and the posture of the terminal device does not change between the first time point and the second time point; in response to rotating the terminal device, at a third time point, displaying a third interface, the third interface is an interface after the second interface is adapted to the rotation of the display screen, the third time point is later than the second time point; based on the user's response to the third interface The operation of the thumbnail of the second image is performed, and at the fourth time point, the second image is set as the desktop wallpaper, and the fourth time point is later than the third time point; in response to the user's operation of returning to the desktop, at the fifth time point, the fourth interface is displayed, and the fourth interface is the interface after the first interface is adapted to the display screen rotation and the wallpaper is changed to the second image, and the fifth time point is later than the fourth time point. Between the third time point and the fourth time point, the desktop application is not started again. Between the fourth time point and the fifth time point, the desktop application does not receive the configuration change information sent by other modules. Between the third time point and the fourth time point, the desktop application receives the configuration change information.

[0007] When the second interface is the interface displayed when the terminal device is in landscape mode, the third interface may be the interface displayed when the terminal device is in portrait mode; or, when the second interface is the interface displayed when the terminal device is in portrait mode, the third interface may be the interface displayed when the terminal device is in landscape mode.

[0008] The fact that the posture of the terminal device has not changed can be understood as the fact that the rotation state (or the horizontal or vertical screen state) of the terminal device has not changed.

[0009] Based on this, when the terminal device detects a combined scenario, such as displaying the desktop, entering the settings application to rotate the screen, setting the wallpaper, and exiting the desktop application, the terminal device can actively obtain configuration change information when it determines that it has not received configuration change information sent by other modules, so that the desktop application can adapt to adjust the desktop layout according to the direction of screen rotation, reducing layout anomalies.

[0010] In one possible implementation, the terminal device is a first device having an outward-folding folding screen, the fourth interface is an interface displayed on the first screen of the outward-folding folding screen, and after displaying the fourth interface, the method further includes: at a sixth time point, displaying a fifth interface on the first screen, the fifth interface including a thumbnail of the first image, and the sixth time point is later than the fifth time point; in response to the operation of folding the first device, at a seventh time point, displaying a sixth interface on the second screen, the sixth interface being an interface after the fifth interface is adapted to the display screen being folded, the second screen being a partial screen of the first screen, and the seventh time point being later than the sixth time point; based on the user's operation on the first image on the sixth interface In response to the user's operation of returning to the desktop, at the ninth time point, the seventh interface is displayed. The seventh interface is the interface after the fourth interface is folded to adapt the display screen and the wallpaper is changed to the first image. The ninth time point is later than the eighth time point. Between the seventh time point and the eighth time point, the desktop application is not started again. Between the eighth time point and the ninth time point, the desktop application does not receive the configuration change information sent by other modules. Between the seventh time point and the eighth time point, the desktop application receives the configuration change information.

[0011] In this way, when the terminal device is a first device with an outward-folding screen, the first device can detect a combined scenario, such as the terminal device displays the desktop, enters the setting application folding screen (or is understood as switching from the device unfolded state to the device folded state), sets the wallpaper, and exits the desktop application. The terminal device can actively obtain configuration change information when it is determined that no configuration change information sent by other modules has been received, so that the desktop application can adapt to adjust the desktop layout according to the folding situation of the screen, reducing layout abnormalities.

[0012] In a possible implementation, the second interface includes a thumbnail of the first image, the thumbnail of the first image includes a check mark, and the thumbnail of the second image does not include a check mark.

[0013] In one possible implementation, the terminal device is configured with a system service and a desktop application. After responding to rotating the terminal device, the method further includes: the system service initiates a first instruction to the desktop application, the first instruction includes information for instructing screen rotation, and the type of the configchange object in the first instruction is a non-resource change type; after the user operates on the thumbnail of the second image on the third interface, the method further includes: the system service initiates a second instruction to the desktop application, the second instruction includes information about the configuration change; the type of the configchange object in the second instruction is a resource change type, and the desktop application sets the first flag to true.

[0014] In this way, the terminal device can use the first flag bit to distinguish the type of configchange object in the sendconfigchange() call, reducing the situation where the system service cannot actively initiate a sendconfigchange() call to the desktop application due to the subsequent setting of configuration items in the desktop application.

[0015] In a possible implementation, the desktop application sets the first flag to true, including: based on the type of the configchange object in the second instruction being a resource change type, the desktop application sets the first flag to true.

[0016] In one possible implementation, after responding to the user returning to the desktop, the method further includes: based on the first flag being true, the desktop application obtains information about configuration changes, and uses the information about configuration changes to display the fourth interface; after the desktop application obtains the information about configuration changes, the desktop application sets the first flag to false.

[0017] In this way, the terminal device can use the first flag bit to distinguish the type of ConfigChange object in the SendConfigChange() call, reducing the situation where the system service cannot actively initiate the SendConfigChange() call to the desktop application due to the configuration items set in the desktop application. Furthermore, the terminal device can set the first flag bit to false to avoid affecting the next judgment of the first flag bit and ensure the accuracy of the solution.

[0018] In one possible implementation, a desktop application is configured with configuration items. Before the desktop application obtains information about configuration changes, the method further includes: the system service notifies the desktop application to start the desktop; the system service obtains the configuration of the desktop application from the desktop application; and the system service does not send information about configuration changes to the desktop application based on the configuration items included in the configuration in the desktop application.

[0019] In one possible implementation, before displaying the first interface, the method also includes: at the tenth time point, displaying the eighth interface, the eighth interface including a first button for determining to set gesture navigation; in response to the operation on the first button, setting gesture navigation; at the eleventh time point, displaying the ninth interface, the ninth interface including a second button for completing the power-on wizard, the eleventh time point is later than the tenth time point; in response to the operation on the second button, at the twelfth time point, the terminal device starts the desktop application, the twelfth time point is later than the eleventh time point; at the thirteenth time point, the desktop application is started, and between the twelfth time point and the thirteenth time point, the desktop application is not started again, and between the twelfth time point and the thirteenth time point, the desktop application does not receive configuration change information sent by other modules.

[0020] In this way, the terminal device can determine that between the twelfth time point and the thirteenth time point, since the desktop application has not received the configuration change information sent by other modules, the desktop application will not be restarted again during the desktop application startup process, preventing the desktop application from writing dirty data to the desktop database when it is started for the second time.

[0021] In one possible implementation, the terminal device is configured with a system service and a desktop application, and the desktop application is configured with configuration items. After the twelfth time point, the method also includes: the system service notifies the desktop application to start the desktop; the system service obtains the configuration of the desktop application from the desktop application; the system service includes the configuration items based on the configuration in the desktop application, and does not send configuration change information to the desktop application.

[0022] In this way, the terminal device can reduce the occurrence of the desktop application being started again in response to an operation on the first button during the desktop startup process by setting the configuration item in the desktop application.

[0023] In a second aspect, an embodiment of the present application provides a desktop display device, which includes a processing unit and a display unit. At a first time point, the display unit is used to display a first interface, which is a desktop and the wallpaper of the first interface is a first image; at a second time point, the display unit is also used to display a second interface, which includes a thumbnail of a second image, and the second time point is later than the first time point; between the first time point and the second time point, the posture of the terminal device does not change; in response to rotating the terminal device, at a third time point, the display unit is used to display a third interface, which is an interface after the second interface is adapted to the rotation of the display screen, and the third time point is later than the second time point; based on the user's The third interface operates on the thumbnail of the second image. At the fourth time point, the processing unit is used to set the second image as the desktop wallpaper. The fourth time point is later than the third time point. In response to the user's operation of returning to the desktop, at the fifth time point, the display unit is used to display the fourth interface. The fourth interface is an interface after adapting the first interface to the display screen rotation and changing the wallpaper to the second image. The fifth time point is later than the fourth time point. Between the third time point and the fourth time point, the desktop application is not started again. Between the fourth time point and the fifth time point, the desktop application does not receive the configuration change information sent by other modules. Between the third time point and the fourth time point, the desktop application receives the configuration change information.

[0024] In a third aspect, an embodiment of the present application provides a terminal device comprising a processor and a memory, the memory being used to store code instructions; the processor being used to run the code instructions so that the terminal device executes the method described in the first aspect or any one of the implementations of the first aspect.

[0025] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores instructions. When the instructions are executed, the computer executes the method described in the first aspect or any implementation of the first aspect.

[0026] In a fifth aspect, a computer program product includes a computer program, which, when executed, enables a computer to execute the method described in the first aspect or any one of the implementations of the first aspect.

[0027] It should be understood that the second to fifth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application;

[0029] FIG2 is a schematic diagram of a software structure of a terminal device provided in an embodiment of the present application;

[0030] FIG3 is a schematic diagram of an interface for performing boot wizard settings according to an embodiment of the present application;

[0031] FIG4 is a flow chart of a method for starting a desktop provided in an embodiment of the present application;

[0032] FIG5 is a flow chart of another method for starting a desktop provided in an embodiment of the present application;

[0033] FIG6 is a schematic diagram of an interface showing an abnormal desktop layout according to an embodiment of the present application;

[0034] FIG7 is a schematic diagram of another interface with abnormal desktop layout provided by an embodiment of the present application;

[0035] FIG8 is a flowchart of another method for starting a desktop provided in an embodiment of the present application;

[0036] FIG9 is a flowchart of another method for starting a desktop provided in an embodiment of the present application;

[0037] FIG10 is a flow chart of an interface display method provided in an embodiment of the present application;

[0038] FIG11 is a schematic structural diagram of a desktop display device provided in an embodiment of the present application;

[0039] FIG12 is a schematic diagram of the hardware structure of another terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. For example, the first value and the second value are merely used to distinguish different values ​​and do not limit their order. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit different values.

[0041] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed 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.

[0042] In this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of 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, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, or a, b and c, where a, b, c can be single or multiple.

[0043] Terminal devices may also be referred to as terminals, user equipment (UE), mobile stations (MS), mobile terminals (MT), etc. Terminal devices may include mobile phones with touch screens, wearable devices, tablet computers (Pads), computers with wireless transceiver functions, and other terminal devices. The mobile phones may include foldable screen phones or large screen phones. Foldable phones include phones with outward-folding screens and phones with inward-folding screens. The embodiments of this application do not limit the specific technologies and device forms used by the terminal devices.

[0044] Therefore, in order to better understand the embodiment of the present application, the structure of the terminal device of the embodiment of the present application is introduced below. For example, Figure 1 is a schematic diagram of the structure of a terminal device provided by the embodiment of the present application.

[0045] The terminal device 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, 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, an indicator 192, a camera 193, and a display screen 194, etc.

[0046] In the embodiment of the present application, the sensor module 180 may include an accelerometer that can identify the posture of the terminal device and detect whether the terminal device switches between landscape and portrait orientations. The accelerometer can detect the magnitude of the terminal device's acceleration in various directions (generally three axes) and, when the terminal device is stationary, can detect the magnitude and direction of gravity.

[0047] In possible implementations, the terminal device may also include one or more of the following sensors, such as: a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, or a bone conduction sensor, etc., which is not specifically limited in the embodiments of the present application.

[0048] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the terminal device. In other embodiments of the present application, the terminal device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0049] The processor 110 may include one or more processing units. The different processing units may be independent devices or integrated into one or more processors. The processor 110 may also be provided with a memory for storing instructions and data.

[0050] USB interface 130 is an interface that complies with USB standards and specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. USB interface 130 can be used to connect a charger to charge the terminal device, or to transfer data between the terminal device and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

[0051] The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. The power management module 141 is used to connect the charging management module 140 to the processor 110.

[0052] The wireless communication function of the terminal device can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

[0053] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. The antennas in a terminal device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0054] Mobile communication module 150 can provide wireless communication solutions for terminal devices, including 2G / 3G / 4G / 5G. It can include at least one filter, switch, power amplifier, and low-noise amplifier (LNA). Mobile communication module 150 receives electromagnetic waves from antenna 1, filters and amplifies the received electromagnetic waves, and transmits them to the modem processor for demodulation.

[0055] The wireless communication module 160 can provide wireless communication solutions applied to terminal devices, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), etc.

[0056] The terminal device implements display functions through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering.

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

[0058] The terminal device can realize the shooting function through the ISP, camera 193, video codec, GPU, display 194 and application processor.

[0059] The camera 193 is used to capture static images or videos. In some embodiments, the terminal device may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0060] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the terminal device. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0061] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 can include a program storage area and a data storage area.

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

[0063] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The speaker 170A, also known as the "speaker", is used to convert audio electrical signals into sound signals. The terminal device can listen to music or listen to hands-free calls through the speaker 170A. The receiver 170B, also known as the "earpiece", is used to convert audio electrical signals into sound signals. When the terminal device answers a call or voice message, the voice can be heard by placing the receiver 170B close to the human ear. The headphone jack 170D is used to connect a wired headset. The microphone 170C, also known as the "microphone" or "microphone", is used to convert sound signals into electrical signals. In an embodiment of the present application, the terminal device may have a microphone 170C.

[0064] The pressure sensor is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor can be set on the display screen 194. The gyroscope sensor can be used to determine the motion posture of the terminal device. The air pressure sensor is used to measure the air pressure. The magnetic sensor includes a Hall sensor. The acceleration sensor can detect the magnitude of the acceleration of the terminal device in various directions (generally three axes). The distance sensor is used to measure the distance. The proximity light sensor can include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The ambient light sensor is used to sense the brightness of the ambient light. The fingerprint sensor is used to collect fingerprints. The temperature sensor is used to detect the temperature. The touch sensor is also called a "touch device". The bone conduction sensor can obtain vibration signals.

[0065] A touch sensor can be provided on display screen 194, and the touch sensor and display screen 194 form a touch screen, or "touch screen." In embodiments of the present application, the touch screen can include a grid of capacitive sensing nodes (hereinafter referred to as a capacitive sensor). When the terminal device determines that the capacitance value of at least one grid received by the capacitive sensor exceeds a capacitance threshold, it can determine that a touch operation has occurred. Furthermore, the terminal device can determine the touch area corresponding to the touch operation based on the area occupied by the at least one grid that exceeds the capacitance threshold.

[0066] Keys 190 include a power button, a volume button, and other buttons. Keys 190 can be mechanical or touch-sensitive. The terminal device can receive key inputs and generate key signal inputs related to user settings and function control of the terminal device. Indicator 192 can be an indicator light that can be used to indicate charging status, battery level changes, messages, missed calls, notifications, and the like.

[0067] The software system of the terminal device can adopt a layered architecture, event-driven architecture, micro-kernel architecture, microservice architecture, or cloud architecture, etc., which will not be described here.

[0068] For example, FIG2 is a schematic diagram of the software structure of a terminal device provided in an embodiment of the present application. As shown in FIG2, the layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into multiple layers, including, from top to bottom, the application (APP) layer, the application framework (framework) layer, the hardware abstraction layer (HAL), and the kernel layer (kernel), etc., which are not limited in the embodiments of the present application.

[0069] The application layer may include a series of application packages. The application layer may include one or more of the following: main application, desktop application, Bluetooth, or phone, etc., which is not limited in the embodiments of the present application.

[0070] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined interfaces. The application framework layer may include one or more of the following: system services, input modules, window managers, content providers, resource managers, view systems, or notification managers. The system services may also include an activity management service (AMS).

[0071] The system service is used to control the desktop application to perform resource changes according to the received trigger event, obtain the configuration of the desktop application, and determine whether to initiate the resource change of the desktop application according to the configuration of the desktop application.

[0072] The AMS is used to control the startup of the desktop application according to the received trigger event, or the AMS can also control the startup of the theme application.

[0073] The input module is used to receive various types of touch events from the user on the terminal device. The touch events may include: press events (or called down events), slide events (or called move events), or lift events (or called up events), etc.

[0074] The window manager is used to manage window programs. For example, the window manager can be used to request the foreground window, obtain the display size, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, take screenshots, etc.

[0075] Content providers are used to store and retrieve data and make it accessible to applications. Data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc. The view system includes visual buttons, such as buttons that display text, buttons that display images, etc. The view system can be used to build applications. The display interface can be composed of one or more views. For example, the display interface that includes a text notification icon can include a view that displays text and a view that displays images. The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0076] The purpose of the hardware abstraction layer is to abstract the hardware. It can provide a unified interface for querying hardware devices for upper-layer applications, or it can also provide data storage services for upper-layer applications. The hardware abstraction layer can include modules such as the hardware composer (HWC).

[0077] The kernel layer is the layer between hardware and software. It drives the hardware to function. This layer can include one or more of the following: display drivers, camera drivers, or sensor drivers.

[0078] The sensor driver is used to detect events detected by sensors and send the events to system services.

[0079] In the embodiments of the present application, no specific limitation is imposed on the software layers involved in the software architecture, the modules contained in the layers, and the functions of the modules.

[0080] The following specific embodiments are used to describe in detail the technical solution of the present application and how the technical solution of the present application solves the above technical problems. The following specific embodiments can be implemented independently or in combination with each other. For the same or similar concepts or processes, some embodiments may not be described in detail.

[0081] Typically, a terminal device can trigger a startup wizard process when it is first started, allowing the user to set the language, map, input method, lock screen password, payment method, gesture navigation or three-button navigation on the screen, etc. The process of setting gesture navigation in the startup wizard process of the terminal device can be seen in the embodiment corresponding to Figure 3.

[0082] Gesture navigation can be understood as controlling a terminal device through gestures on the display. For example, in response to a user swiping upward from the bottom of the display, the terminal device can display the desktop; or, in response to a user swiping along the left or right side of the display, the terminal device can return to the previous interface of the current interface; or, in response to a user swiping upward from the bottom of the display and pausing, the terminal device can display the multitasking interface; or, in response to a user swiping in an arc along the bottom edge of the display, the terminal device can quickly switch applications. The gesture operations supported by the terminal device are not limited to the above, and will not be detailed here.

[0083] The three-button navigation system on the screen can be understood as controlling the terminal device through three virtual buttons displayed at the bottom of the display screen. These three virtual buttons are composed of a small square, a small circle, and a small triangle. For example, in response to the user's click on the small square, the terminal device can return to the previous interface of the current interface; in response to the user's click on the small circle, the terminal device can display the desktop; in response to the user's click on the small triangle, the terminal device can display the multitasking interface.

[0084] It is understandable that compared to controlling the terminal device through three-button navigation on the screen, gesture navigation has a larger operating range and can minimize the system drawing virtual buttons on the application content.

[0085] For example, Figure 3 is a schematic diagram of an interface for setting up a startup wizard provided in an embodiment of the present application. In the embodiment corresponding to Figure 3, an example is given of a foldable screen mobile phone (or a terminal device with an inward-folding screen), which does not constitute a limitation on the embodiments of the present application.

[0086] The terminal device can display an interface as shown in a in Figure 3 when it is started for the first time. This interface can be called the first interface of the startup wizard. This interface is used to implement language settings. The interface displays: at least one button for setting the language, a button 301 for starting to enable the terminal device, a button for triggering an emergency call, and a button for triggering assisted reading. In this interface, the terminal device can select Simplified Chinese as the language by default.

[0087] When the terminal device detects a user triggering operation on button 301, the terminal device may display the interface shown in FIG3 b after displaying multiple other setting interfaces in the startup wizard. The interface shown in FIG3 b can be called a gesture navigation setting interface, which can be used to set the navigation mode. The interface may display: a return button, a next button 302, and a button for changing the navigation mode.

[0088] The terminal device may default to gesture navigation as the navigation mode of the terminal device. For example, when the terminal device detects that the user triggers the next button 302, the terminal device confirms that gesture navigation is used and displays the interface shown in Figure 3c. Alternatively, the user can also change the navigation mode to three-button navigation on the screen by triggering the button for changing the navigation mode.

[0089] In response to the user's triggering operation on the next button 302, the terminal device can call sendconfigchange() to enable the desktop application to change resources, and then the desktop application executes the desktop startup process.

[0090] The interface shown in c in Figure 3 can be called the startup wizard completion interface, which can be used to view the precautions for using the terminal device. The interface can display: a completion button 303, text information corresponding to the precautions, and a return button.

[0091] When the terminal device detects the user's trigger operation on the completion button 303, the terminal device can display the interface shown in d in Figure 3, which can be a desktop interface. The desktop interface is used to view the various applications of the terminal device. For example, the interface can display: settings application icon, gallery application icon, document management application icon, and a fixed bar placed at the bottom of the display screen. The fixed bar can display: alarm clock application icon, computer application icon, mailbox application icon, phone application icon and memo application icon.

[0092] In response to the user's triggering operation on the completion button 303, the terminal device can call startactivity() to enable the desktop application to start the desktop.

[0093] It is understandable that since both triggering the Next button 302 and triggering the Finish button 303 can realize desktop startup, when the terminal device initiates the step of sendconfigchange() in response to the user's triggering operation on the Next button 302 slowly, or the terminal device initiates the step of desktop startup in response to the user's triggering operation on the Finish button 303 quickly, the terminal device may detect that the terminal device is restarting the desktop in response to the Next button 302 during the process of desktop startup in response to the user's triggering operation on the Finish button 303, and during the desktop restart process, the terminal device writes dirty data to the desktop database, resulting in the desktop being unable to complete normal loading and the desktop display being abnormal.

[0094] During the two desktop launches, the terminal device writes application icon data to the desktop database. Due to the duplication of application icon data, the desktop cannot load normally. Consequently, the icon layout actually displayed on the desktop may differ from the terminal device's preset icon layout, causing desktop display anomalies. For example, an application's icon may be preset in the first position in the upper left corner of a certain interface, but due to a desktop display anomaly, the application's icon may be displayed in the lower right corner of the interface.

[0095] Dirty data can be understood as the application icon data written to the desktop database when the terminal device responds to the next button 302 to start the desktop. The application icon data may include: the coordinate position of the application icon, the width and height of the application icon, and the name of the application icon, etc.

[0096] On the basis of the embodiment corresponding to FIG. 3 , the terminal device may illustrate the desktop startup process twice in the startup wizard based on the embodiment corresponding to FIG. 4 .

[0097] For example, Figure 4 is a flowchart of a method for starting a desktop provided in an embodiment of the present application. In the embodiment corresponding to Figure 4, the terminal device may include: a desktop application, a system service, and an input module, and the system service may include an AMS.

[0098] As shown in FIG4 , the method for starting the desktop may include the following steps:

[0099] S401: In response to a user triggering a next button, the input module sends a first trigger event to a system service.

[0100] The next button may be the next button 302 in the interface shown in b of FIG. 3 .

[0101] The first trigger event may include: a down event for the next button 302 , and an up event for the next button 302 .

[0102] Typically, when a system service detects a first trigger event, it can call sendconfigchange() to send configuration (or resource) change information to the background application. When the desktop application receives sendconfigchange(), the desktop application triggers desktop startup.

[0103] sendconfigchange() is a function that notifies configuration changes. Applications can make resource changes based on the received sendconfigchange().

[0104] SendConfigChange() may include a ConfigChange object. ConfigChange may be understood as a configuration change. The ConfigChange object may include configuration change content. For example, the ConfigChange object may include one or more of the following information, such as screen size information, display orientation information, and the type of the ConfigChange object.

[0105] The configchange object type can be either resource change or non-resource change. Resource changes can include wallpaper changes, while non-resource changes can include one or more of the following: dark mode / light mode changes, device expansion / folding changes, or device rotation (also known as device size changes).

[0106] In the sendconfigchange() call actually initiated by the terminal device, the resource change type or non-resource change type can be carried in sendconfigchange() with a corresponding type identifier.

[0107] Since the terminal device calls sendconfigchange() to send the resource change instruction to the desktop application late, or the user triggers the completion button 303 quickly, the terminal device calls sendconfigchange() in response to the first trigger event after executing S403. It can be understood that the terminal device did not initiate the step of calling sendconfigchange() in S404 after S401, but executed the step shown in S404 after executing S403.

[0108] S402: In response to the user triggering the completion button, the input module sends a second trigger event to the system service.

[0109] The finish button may be the finish button 303 in the interface shown in c of FIG. 3 .

[0110] The second trigger event may include: a down event for the completion button 303 , and an up event for the completion button 303 .

[0111] Before S403 , the desktop application is in the background; in S403 , after the terminal device starts the desktop, the desktop application is in the foreground.

[0112] Among them, foreground and background are usually used to describe the state of an application at runtime.

[0113] Specifically, when the application interface is being displayed, the application is in the foreground, and the application is in the onresume state.

[0114] Background applications are still running, but their UI is no longer displayed on the screen. Applications running in the background can perform lightweight operations, such as receiving notifications and monitoring network changes, but their resource usage and priority are generally lower.

[0115] S403: The AMS in the system service calls startactivity(), and the desktop application starts the desktop.

[0116] startactivity() is a function that starts an activity.

[0117] After S403 , the desktop application executes the desktop loading process, and during the desktop loading process, the desktop switches from the background to the foreground, and the system service executes the steps shown in S404 in response to the first triggering event.

[0118] S404: The system service calls sendconfigchange(), and the desktop application performs resource changes.

[0119] In sendconfigchange(), the type of the configchange object can be a resource change type.

[0120] It is understandable that when the configchange object type is resource change type, the desktop starts. During the desktop startup process, the system service may write dirty data to the desktop database, causing the desktop application to fail to load normally and the desktop display to be abnormal.

[0121] Based on the embodiment corresponding to FIG4 , the terminal device can set the avoid restart configuration item avoid_rro_relaunch to ensure that the system service does not initiate a sendconfigchange() call.

[0122] For example, FIG5 is a flowchart of another method for starting a desktop provided in an embodiment of the present application.

[0123] As shown in FIG5 , the method for starting the desktop may include the following steps:

[0124] S501: In response to a user triggering a next button, the input module sends a first trigger event to a system service.

[0125] S502: In response to the user triggering the completion button, the input module sends a second trigger event to the system service.

[0126] S503: The AMS in the system service calls startactivity(), and the desktop application starts the desktop.

[0127] The steps shown in S503-S501 can refer to the description of the steps shown in S401-S403, and will not be repeated here.

[0128] After S503 , the desktop application executes a desktop loading process, and during the desktop loading process, the desktop may be switched from the background to the foreground.

[0129] S504: The system service calls getmetadata() to obtain the configuration of the desktop application.

[0130] getmetadata() is a function for obtaining metadata. Metadata is information that describes data. For example, a system service can obtain metadata in a desktop application through getmetadata().

[0131] The configuration of the desktop application may include: a configuration item avoid_rro_relaunch.

[0132] Each application can configure the configuration item avoid_rro_relaunch separately. When a target application is configured with avoid_rro_relaunch, the target application will not receive the sendconfigchange() call initiated by the system service. Exemplarily, when the target application is configured with avoid_rro_relaunch, the system service may not initiate a sendconfigchange() call to the target application based on avoid_rro_relaunch when responding to the step shown in S501.

[0133] In a possible implementation, when the target application is not configured with avoid_rro_relaunch, the system service will initiate an endconfigchange() call to the target application in response to the step shown in S501. At this time, the target application will receive sendconfigchange(), and then the target application will trigger the startup process.

[0134] S505: The system service determines whether the configuration item avoid_rro_relaunch exists.

[0135] When the system service determines that the configuration item avoid_rro_relaunch exists, the system service does not initiate a sendconfigchange() call; or, when the system service determines that the configuration item avoid_rro_relaunch does not exist, the system service executes the step shown in S506.

[0136] When the system service determines that avoid_rro_relaunch is true, it is determined that the configuration item exists; or when the system service determines that avoid_rro_relaunch is not true, it is determined that the configuration item does not exist.

[0137] S506: The system service calls sendconfigchange(), and the desktop application performs resource changes.

[0138] The steps shown in S506 can refer to the description of the steps shown in S404 and will not be repeated here.

[0139] Based on this, the system service can detect the configuration item avoid_rro_relaunch in the desktop application, avoid initiating a sendconfigchange() call and desktop startup to the desktop application, and then the desktop application cannot restart the desktop during the desktop loading process, thus avoiding the situation where dirty data is written to the desktop database during the process of restarting the desktop.

[0140] In a possible implementation, the system service can initiate a sendconfigchange() call to the desktop application after executing S505, and not initiate a start instruction to the desktop application. The desktop application can receive the sendconfigchange() call but cannot receive the instruction to start the desktop, and can also avoid starting the desktop again during the desktop loading process.

[0141] In the embodiment corresponding to Figure 5, based on the fact that the terminal device avoids initiating a sendconfigchange() call to the desktop by setting avoid_rro_relaunch, when the terminal device appears in a combined scenario, the terminal device displays the desktop in landscape mode, switches to portrait mode to set wallpaper, and then returns to the foreground, the terminal device may have an abnormal desktop layout.

[0142] For example, FIG6 is a schematic diagram of an interface with an abnormal desktop layout provided in an embodiment of the present application.

[0143] The terminal device can display the interface as shown in a in Figure 6 in horizontal screen, which can be the desktop interface of the terminal device, which is used to view the various applications of the terminal device. The desktop can display: schedule cards, daily news cards, settings application icons, gallery application icons, document management application icons, and a fixed bar placed at the bottom of the display screen. The fixed bar can display: alarm clock application icon, computer application icon, mailbox application icon, phone application icon and memo application icon. The interface can also display wallpaper, and the wallpaper can display trees and mountains.

[0144] Upon detecting a user triggering an action on the settings app icon, the terminal device may enter the settings app and display the homepage of the settings app. When the terminal device enters the settings app, upon detecting a user switching the screen from landscape to portrait orientation, the terminal device may adaptively switch the content displayed on the terminal device.

[0145] In response to the user's operation of switching from landscape to portrait mode, the terminal device initiates a sendconfigchange() call to the background application to notify the background desktop application to rotate the screen.

[0146] Upon detecting that a user has opened the wallpaper selection interface in the Settings app by following the path "Desktop & Wallpaper -> Set Wallpaper," the terminal device may display the interface shown in FIG6(b) in portrait mode. The interface shown in FIG6(b) may be a wallpaper selection interface for viewing images provided by the terminal device. The interface may display: a button for opening the gallery, a thumbnail corresponding to at least one image, such as thumbnail 600 and thumbnail 601, and a button for viewing more wallpapers. Thumbnail 600 may display a check mark, while thumbnail 601 may not. As shown in FIG6 , the check mark may include a check mark.

[0147] When the terminal device detects the user's trigger operation on the thumbnail 601, the terminal device displays the interface shown in c in Figure 6 in portrait mode. The interface is the wallpaper setting interface, which is used to set the selected wallpaper. The interface can display: the image corresponding to the thumbnail 601 and the button 602 for applying it as wallpaper.

[0148] When the terminal device detects that the user has triggered button 602, the terminal device may set the image corresponding to thumbnail 601 as the desktop wallpaper of the terminal device. In response to the user triggering button 602, the terminal device may display an interface for selecting a wallpaper. In this interface, there is no selection mark in thumbnail 600, but there is a selection mark in thumbnail 601. It can be understood that the terminal device has set the image corresponding to thumbnail 601 as the desktop wallpaper at this time, which is not shown in Figure 6.

[0149] In response to the user's operation of setting the desktop wallpaper, the terminal device initiates a sendconfigchange() call to the background application to notify the background desktop application to make resource changes.

[0150] It is understandable that when the terminal device sets the image corresponding to thumbnail 600 as the desktop wallpaper, the terminal device may also initiate a sendconfigchange() call to the background application. In this scenario, the desktop wallpaper is not switched, but an operation of setting the wallpaper is triggered. This is not limited in the embodiments of the present application.

[0151] After the wallpaper is set, when the terminal device detects the user's operation to return to the desktop, the terminal device can exit the current interface and return to the desktop, such as the interface shown in Figure 6 (d) in the vertical screen of the terminal device. The user's operation to return to the desktop can be an operation of the user swiping upward along the bottom of the display screen. In the interface shown in Figure 6 (d), the terminal device can display the desktop layout when the terminal device is in landscape mode in portrait mode, resulting in an abnormal desktop layout.

[0152] In response to the user swiping upward along the bottom of the interface shown in b in Figure 6, the terminal device can modify the type of the configchange object from a resource change type to a non-resource change type when determining the existence of the configuration item avoid_rro_relaunch. The non-resource change type sendconfigchange() call can be used to rotate the screen. Furthermore, the two non-resource change type sendconfigchange() calls result in the desktop's horizontal and vertical states not changing, and the terminal device will not trigger the resource change type sendconfigchange(), resulting in the terminal device displaying a horizontal desktop layout in the vertical state.

[0153] It is understandable that the combination scenarios that affect the desktop layout may not be limited to the description in Figure 6. For example, when the terminal device displays combination scenario 1, displays the desktop in portrait mode, enters the settings function and switches to landscape mode to set the wallpaper, and then returns to the foreground, or when the terminal device displays combination scenario 2, when the terminal device displays the desktop by expanding the device, enters the settings function and folds the device to set the wallpaper, and then returns to the foreground, or when the terminal device displays combination scenario 3, when the terminal device displays the desktop by folding the device, enters the settings function and expands the device to set the wallpaper, and then returns to the foreground, the terminal device may have an abnormal desktop layout as shown in Figure 6, and the specific solutions are similar to those described in Figure 8, which will not be repeated here.

[0154] For example, when the terminal device is a first device with an outward-folding screen, Figure 7 will take combination scenario 2 as an example to illustrate the specific situation in which the device expansion / device folding changes affect the desktop layout. Figure 7 is an interface diagram of another abnormal desktop layout provided in an embodiment of the present application.

[0155] When the first device is in the expanded state, the first device can display the interface shown in a in Figure 7 on the first screen. The interface can be the desktop interface of the first device. The content displayed in the interface can be similar to the content displayed in the interface shown in a in Figure 6, and will not be repeated here.

[0156] Upon detecting a user triggering an operation on a settings application icon, the first device may enter the settings application and display the settings application homepage or another interface within the settings application, such as a wallpaper selection interface. When the first device enters the settings application, upon detecting a user folding the first device, the first device may display the contents of the settings application on the second screen of the first device and turn off the third screen of the first device.

[0157] In response to the user's operation of folding the first device, the first device initiates a sendconfigchange() call to the background application to notify the desktop application in the background to fold the screen.

[0158] The second screen can also be called the main screen, and the third screen can also be called the back screen or auxiliary screen. The first screen, second screen and third screen are all different display areas in the display screen. The area of ​​the second screen can be larger than the area of ​​the third screen, and the area of ​​the first screen can be larger than the area of ​​the second screen.

[0159] It is understandable that when the user folds the first device, the third screen can be turned off and leaned against the second screen. In order to distinguish between the second and third screens, the embodiment of the present application provides an example of the state displayed on the third screen. In the interface shown in FIG7 b, the third screen is turned off. The content displayed on the second screen in the interface shown in FIG7 b is similar to the content displayed in the interface shown in FIG6 b, and will not be repeated here.

[0160] When the first device detects the user's trigger operation on the thumbnail 701, the first device displays the interface of the second screen in c in Figure 7, which is the wallpaper setting interface. The interface is used to set the selected wallpaper. The interface can display: the image corresponding to the thumbnail 701, and the button 702 for applying it as wallpaper.

[0161] When the first device detects a user triggering operation on button 702 , the first device may set the image corresponding to thumbnail 701 as the desktop wallpaper of the first device.

[0162] In response to the user's operation of setting the desktop wallpaper, the first device initiates a sendconfigchange() call to the background application to notify the background desktop application to make resource changes.

[0163] After the wallpaper is set, when the first device detects that the user has returned to the desktop, the first device may exit the current interface and return to the desktop, such as the first device displaying the interface of the second screen in d of Figure 7. As shown in d of Figure 7, the second screen of the first device displays the desktop layout when the first device is in the expanded state, resulting in an abnormal desktop layout.

[0164] In FIG. 7 b to FIG. 7 d , since the first device is in a folded state, the third screen is off.

[0165] Among them, in response to the user sliding upward along the bottom of the interface shown in b in Figure 7, the first device may not trigger the resource change type sendconfigchange() when determining that there is a configuration item avoid_rro_relaunch, causing the first device to display the desktop layout when the device is in an unfolded state in a folded state.

[0166] It is understandable that when the combination scene 3 appears on the first device, a desktop layout anomaly similar to the scene described in the embodiment corresponding to FIG7 may also occur, which will not be described in detail here.

[0167] On the basis of the embodiment corresponding to FIG6 , the terminal device may describe the device execution logic in the combined scenario based on the embodiment corresponding to FIG8 .

[0168] For example, FIG8 is a flowchart illustrating another method for launching a desktop provided in an embodiment of the present application. In the embodiment corresponding to FIG8 , the terminal device may include: a desktop application, a system service, an input module, and a sensor driver. The system service may include an AMS. The event received by the sensor driver may be an event acquired by a sensor for identifying the device's horizontal or vertical screen switching. The sensor for identifying the device's horizontal or vertical screen switching may be an accelerometer.

[0169] S801: In response to a user rotating the device to a vertical position, the sensor driver may send a third trigger event to the system service.

[0170] The user's operation of rotating the device to portrait mode can be an operation in which the user switches from landscape mode to portrait mode in the Settings app.

[0171] The third trigger event can be understood as a rotation event for the device, and the third trigger event may include information that the terminal device is rotated to a vertical screen.

[0172] S802: The system service initiates a sendconfigchange() call to the background application.

[0173] The type of the configchange object in sendconfigchange() described in S802 is the device rotation change in the non-resource call type.

[0174] Background applications may include desktop applications. SendConfigChange() may be sent by the system service to the desktop application in the background. When the desktop application receives SendConfigChange(), it may determine to rotate the screen according to the information carried in SendConfigChange().

[0175] S803: In response to the user's operation of setting wallpaper, the input module sends a fourth trigger event to the system service.

[0176] The user's operation of setting the wallpaper may be a triggering operation of the user on the button 602 in the interface shown in c of FIG. 6 .

[0177] The fourth trigger event may include: a down event for the button 602 and an up event for the button 602 .

[0178] S804: The system service sends a fourth trigger event to the theme application.

[0179] S805: In response to the fourth triggering event, the theme application sets a wallpaper.

[0180] S806: The theme application sends a message to the system service indicating that the wallpaper setting is completed.

[0181] S807. The AMS in the system service restarts the theme application.

[0182] For example, when the system service determines that the wallpaper setting is completed, the AMS closes the theme application and starts the theme application by calling startactivity().

[0183] S808: The system service initiates a sendconfigchange() call to the background application, and the desktop application performs resource changes.

[0184] The type of the configchange object in sendconfigchange() described in S808 is a resource call type.

[0185] Background applications may include desktop applications. SendConfigChange() can be sent by the system service to the desktop application in the background. When receiving SendConfigChange(), the desktop application can determine to make resource changes based on the configuration change information carried in SendConfigChange(). For example, the desktop application sets the wallpaper based on the configuration change information.

[0186] S809: In response to the user sliding back to the desktop, the input module sends a fifth trigger event to the system service.

[0187] The operation of the user sliding up to return to the desktop may be an operation of the user sliding upward on the bottom end of the interface shown in b in FIG. 6 .

[0188] The fifth trigger event may include: a down event for the interface shown in b in FIG. 6 , an up event for the interface shown in b in FIG. 6 , and a sliding event (move event) for the interface shown in b in FIG. 6 .

[0189] S810: The system service sends a fifth trigger event to the desktop application.

[0190] S811: The desktop application receives the fifth trigger event and determines whether the condition for sliding up to return to the desktop is met.

[0191] Exemplarily, the desktop application can calculate data such as the distance the user swipes up and the speed when raising the hand through the parameters in the fifth trigger event, and then when it is determined that the distance of the swipe up is greater than the distance threshold and the speed when raising the hand is greater than the speed threshold, and when it is determined that the desktop application meets the conditions for swiping up to return to the desktop, execute the steps shown in S812.

[0192] S812. The desktop application calls AMS through onstart() to pull up the desktop interface.

[0193] Onstart() is a function used to load visible resources when an activity switches from invisible to visible. For example, onstart() can initialize the desktop interface.

[0194] S813. The AMS in the system service calls startactivity(), and the desktop application starts the desktop.

[0195] S814. The system service calls getmetadata() to obtain the configuration of the desktop application.

[0196] The configuration of the desktop application may include: a configuration item avoid_rro_relaunch. The function of avoid_rro_relaunch can be found in the description of S504 and will not be repeated here.

[0197] S815. The system service determines whether the configuration item avoid_rro_relaunch exists.

[0198] When the system service determines that the configuration item avoid_rro_relaunch exists, the system service does not initiate a sendconfigchange() call; or, when the system service determines that the configuration item avoid_rro_relaunch does not exist, the system service executes the step shown in S816.

[0199] S816. The system service initiates a sendconfigchange() call, and the desktop application performs resource changes.

[0200] It is understandable that when the system service determines that the configuration item does not exist, the system service can change the type of the configchange object in S808 from the resource type in the previous method call to the non-resource change type in S802. The system service can now confirm that it has received two non-resource change type sendconfigchange() calls, and the two non-resource change type sendconfigchange() calls are used to implement screen rotation. The two screen rotations cancel each other out, which is equivalent to the desktop layout not changing. The system service can then determine not to initiate a resource change type sendconfigchange() call to the desktop application. In this scenario, the terminal device in portrait mode can see the horizontal screen desktop layout as shown in d in Figure 6.

[0201] In possible implementations, in addition to the device rotation changes described in the embodiment corresponding to Figure 8, when the terminal device is the first device with an outward-folding screen, the device expansion / device folding changes can also affect the desktop layout of the terminal device, and the process of desktop layout abnormality is similar to Figure 7, which will not be repeated here.

[0202] Based on the embodiment corresponding to Figure 8, the terminal device can mark the type of the configchange object by setting the resource change flag misresourcechange, which may include a resource change type or a non-resource change type, and actively trigger the configuratinchanged() call when it is determined that misresourcechange is true (or understood that the type of the configchange object is a resource change type).

[0203] For example, FIG9 is a flowchart of another method for starting a desktop provided in an embodiment of the present application.

[0204] S901: In response to a user rotating the device to a vertical position, the sensor driver may send a third trigger event to the system service.

[0205] S902: The system service initiates a sendconfigchange() call to the background application.

[0206] S903: In response to the user's operation of setting wallpaper, the input module sends a fourth trigger event to the system service.

[0207] S904: The system service sends a fourth trigger event to the theme application.

[0208] S905: In response to the fourth triggering event, the theme application sets a wallpaper.

[0209] S906: The theme application sends a message to the system service indicating that the wallpaper setting is completed.

[0210] S907. The AMS in the system service restarts the theme application.

[0211] S908: The system service initiates a sendconfigchange() call to the background application, and the desktop application performs resource changes.

[0212] The steps shown in S901-S908 can refer to the description of the steps shown in S801-S808, and will not be repeated here.

[0213] Among them, sendconfigchange() can carry the type identifier of the configchange object, and the type identifier corresponding to the resource change type can be 0x80000000. It can be understood that when sendconfigchange() carries 0x80000000, the desktop application can determine that the type of the configchange object is the resource change type.

[0214] S909: When the type of the configchange object is a resource change type, the desktop application marks misresourcechange as true.

[0215] "misresourcechange" can be understood as a resource change flag. Different values ​​of "misresourcechange" correspond to different resource change types when initiating "configchange()." For example, "misresourcechange" being true indicates that the "configchange" object in the "sendConfigChange()" call initiated by the system service is a resource change object; "misresourcechange" being false indicates that the "configchange" object in the "sendConfigChange()" call initiated by the system service is a non-resource change object.

[0216] In a possible implementation, when the type of the configchange object is not a resource change type, the desktop application may mark misresourcechange as false or may not mark the type.

[0217] S910: In response to the user sliding back to the desktop, the input module sends a fifth trigger event to the system service.

[0218] S911. The system service sends a fifth trigger event to the desktop application.

[0219] S912. In response to the fifth triggering event, the desktop application determines to return to the desktop.

[0220] S913. The desktop application calls AMS through onstart() to pull up the desktop interface.

[0221] The steps shown in S914-S921 can be understood as the steps executed in the onstart() process.

[0222] S914. The AMS in the system service calls startactivity(), and the desktop application starts the desktop.

[0223] S915. The system service calls getmetadata() to obtain the configuration of the desktop application.

[0224] The configuration of the desktop application may include: a configuration item avoid_rro_relaunch.

[0225] S916. The system service determines whether the configuration item avoid_rro_relaunch exists.

[0226] When the system service determines that the configuration item avoid_rro_relaunch exists, the system service executes the step shown in S917; or, when the system service determines that the configuration item avoid_rro_relaunch does not exist, the system service does not initiate the sendconfigchange() call.

[0227] S917. The system service initiates a sendconfigchange() call, and the desktop application performs resource changes.

[0228] Among them, the steps shown in S910-S917 can refer to the description of the steps shown in S809-S816, and will not be repeated here.

[0229] Exemplarily, the terminal device may sequentially execute steps S918-S920 after completing the judgment logic of S916-S917.

[0230] S918. The desktop application determines whether misresourcechange is true.

[0231] When the desktop application determines that misresourcechange is true, the desktop application executes the step shown in S919; alternatively, when the desktop application determines that misresourcechange is not true, the desktop application does not initiate a configureInchanged() call.

[0232] S919. The desktop application calls configure_inchanged() to obtain desktop resources.

[0233] For example, a desktop application can obtain desktop resources by actively calling configure_inchanged(). For example, by determining through configure_inchanged() that the terminal device is in portrait mode, the desktop application can adjust the layout structure of the desktop according to the portrait mode so that the desktop application can be displayed normally in the portrait mode.

[0234] S920. The desktop application sets misresourcechange to false.

[0235] It is understandable that the desktop application may set misresourcechange to false after determining the value of misresourcechange, so as to avoid affecting the next determination in S918.

[0236] Based on this, the terminal device can mark the resource change type sendconfigchange() by setting the flag bit misresourcechange, and actively trigger desktop resource acquisition when misresourcechange is true to determine the landscape or portrait state of the terminal device. This can avoid the terminal device changing the resource change type sendconfigchange() to the non-resource change type sendconfigchange(). The two non-resource change type sendconfigchange() offset each other, causing the terminal device to determine that the desktop has not changed, and thus unable to trigger the non-resource change type sendconfigchange() call, resulting in desktop layout abnormalities.

[0237] It is understandable that when the terminal device is a first device with an outward-folding screen, the first device can also reduce the occurrence of the combination scenario shown in Figure 7 by marking the misresourcechange flag. The specific process is similar to that described in Figure 9 and will not be repeated here.

[0238] In conjunction with the embodiment corresponding to FIG9 , FIG10 is a flow chart of an interface display method provided in an embodiment of the present application. The desktop display method may include the following steps:

[0239] S1001. At a first time point, display a first interface.

[0240] The first interface is the desktop, and the wallpaper of the first interface is the first image.

[0241] The first interface may be the interface shown in a in FIG. 6 , and the first image may be the image displayed on the desktop wallpaper in the interface shown in a in FIG. 6 .

[0242] S1002. At a second time point, display a second interface.

[0243] The second interface includes a thumbnail of a second image. The second time point is later than the first time point. The posture of the terminal device does not change between the first time point and the second time point.

[0244] The second interface may be an interface displayed on the terminal device before the screen is rotated, or may be an interface displayed when the terminal device is in landscape mode. The content displayed in this interface may be the same as the content displayed in the interface shown in FIG6 b, and the second image may be the image indicated in thumbnail 600. It can be understood that the first image and the second image may be the same or different.

[0245] When the first image is different from the second image, the interface shown in b in Figure 6 may include a thumbnail 600 of the first image and a thumbnail 601 of the second image. Since the first image is the desktop wallpaper at this time, the thumbnail of the first image may be in a selected state and the thumbnail of the second image may be in a non-selected state.

[0246] S1003: In response to rotating the terminal device, displaying a third interface at a third time point.

[0247] The third interface is the interface after the second interface is adapted to the display screen is rotated, and the third time point is later than the second time point.

[0248] The third interface may be an interface displayed by the terminal device in a vertical screen state, such as the interface shown in b in FIG. 6 .

[0249] In response to rotating the terminal device, the terminal device executes steps S901-S902, the system service initiates a sendconfigchange() call to the background application, the rotation causes the horizontal and vertical screen states of the second interface to change, and the terminal device displays the third interface.

[0250] S1004: Based on the user's operation on the thumbnail of the second image on the third interface, at a fourth time point, set the second image as the desktop wallpaper.

[0251] The fourth time point is later than the third time point.

[0252] The user's operation on the thumbnail of the second image in the third interface may be an operation of setting the image corresponding to the thumbnail 601 as wallpaper in the interface shown in b of FIG. 6 .

[0253] In response to the user's operation on the thumbnail of the second image on the third interface, the terminal device executes steps shown in S903-S908, and the system service initiates a sendconfigchange() call to the background application, so that the desktop application sets the second image as the desktop wallpaper based on the configuration change information contained in the sendconfigchange() call.

[0254] S1005. In response to the user's operation of returning to the desktop, at a fifth time point, displaying a fourth interface.

[0255] The fourth interface is the interface after the first interface is adapted to the display screen rotation and the wallpaper is changed to the second image. The fifth time point is later than the fourth time point. Between the third time point and the fourth time point, the desktop application is not started again. Between the fourth time point and the fifth time point, the desktop application does not receive the configuration change information sent by other modules. Between the third time point and the fourth time point, the desktop application receives the configuration change information.

[0256] For example, the fourth interface may be an interface displayed when the terminal device is in portrait mode. The desktop layout displayed in this interface may be the same as the desktop layout displayed in the interface shown in a in FIG. 6 , and will not be described in detail here.

[0257] In response to the user returning to the desktop, the terminal device executes steps S910-S920. The system service does not initiate a call to sendconfigchange() if it determines that the desktop application has an avoid_rro_relaunch condition. Instead, it proactively initiates a call to configureuratingchanged() if it determines that misresourcechange is true. The desktop application can obtain configuration change information based on the call to configureuratingchanged() and implement a reasonable desktop layout, such as the desktop layout when the terminal device is in portrait mode.

[0258] Among them, between the third time point and the fourth time point, the desktop application of the terminal device is in the background, and the desktop application is not started again.

[0259] Between the fourth time point and the fifth time point, the desktop application did not receive the configuration change information sent by other modules. It can be understood that after the system service determined not to send sendconfigchange() based on the existence of the configuration item determined in S916, the desktop application did not receive the configuration change information. Other modules may include system services.

[0260] Between the third time point and the fourth time point, the desktop application receives configuration change information, which can be understood as the sendconfigchange() obtained by the desktop application from the system service in S908.

[0261] Between the fourth time point and the fifth time point, the desktop application obtains the configuration change information, which can be understood as the desktop application obtaining the configuration change information based on the configure_inchanged() actively initiated in S919.

[0262] In a possible implementation, in addition to rotating the screen, folding or unfolding changes of the device may also trigger similar desktop display abnormalities.

[0263] For example, the terminal device is a first device with an outward-folding folding screen, the fourth interface is an interface displayed on the first screen of the outward-folding folding screen, and after displaying the fourth interface, the method further includes: at a sixth time point, displaying a fifth interface on the first screen, the fifth interface including a thumbnail of the first image, and the sixth time point is later than the fifth time point; in response to the operation of folding the first device, at a seventh time point, displaying a sixth interface on the second screen, the sixth interface is an interface after the fifth interface is adapted to the display screen being folded, the second screen being a partial screen of the first screen, and the seventh time point is later than the sixth time point; based on the user's thumbnail of the first image on the sixth interface operation, at the eighth time point, the first image is set as the desktop wallpaper, and the eighth time point is later than the seventh time point; in response to the user's operation of returning to the desktop, at the ninth time point, the seventh interface is displayed, and the seventh interface is the interface after the fourth interface is folded to adapt the display screen and the wallpaper is changed to the first image, and the ninth time point is later than the eighth time point. Between the seventh time point and the eighth time point, the desktop application is not started again. Between the eighth time point and the ninth time point, the desktop application does not receive the configuration change information sent by other modules. Between the seventh time point and the eighth time point, the desktop application receives the configuration change information.

[0264] For the first screen and the second screen, please refer to the corresponding description of Figure 7.

[0265] The fourth interface may also be the interface displayed on the first screen shown in a of FIG. 7 , and the fifth interface may be the interface displayed on the first screen by the first device as shown in b of FIG. 6 . The sixth interface may be the interface displayed on the second screen shown in b of FIG. 7 , and the seventh interface may be the interface displayed when the first device displays the complete content of the interface shown in a of FIG. 7 on the second screen.

[0266] Since the solution to the desktop layout abnormality of the first device is similar to the solution when the terminal device rotates, the steps performed by the first device in response to different user operations are similar to those described in Figure 10 and are not repeated here.

[0267] In one possible implementation, the terminal device includes: a system service, a desktop application. After responding to rotating the terminal device, the method further includes: after responding to rotating the terminal device, the method further includes: the system service initiates a first instruction to the desktop application, the first instruction includes information for instructing screen rotation, and the type of the configchange object in the first instruction is a non-resource change type; after based on the user's operation on the thumbnail of the second image on the third interface, the method further includes: the system service initiates a second instruction to the desktop application, the second instruction includes information about the configuration change; the type of the configchange object in the second instruction is a resource change type, and the desktop application sets the first flag to true.

[0268] The first instruction may be the call of sendconfigchange() described in S802 or S902. The second instruction may be the call of sendconfigchange() described in S808 or S908.

[0269] In one possible implementation, after responding to the user returning to the desktop, the method further includes: based on the first flag being true, the desktop application obtains information about configuration changes, and uses the information about configuration changes to display the fourth interface; after the desktop application obtains the information about configuration changes, the desktop application sets the first flag to false.

[0270] The first flag may be misresourcechange.

[0271] In one possible implementation, a desktop application is configured with configuration items. Before the desktop application obtains information about configuration changes, the method further includes: the system service notifies the desktop application to start the desktop; the system service obtains the configuration of the desktop application from the desktop application; and the system service does not send information about configuration changes to the desktop application based on the configuration items included in the configuration in the desktop application.

[0272] The configuration item can be avoid_rro_relaunch.

[0273] In one possible implementation, before displaying the first interface, the method also includes: before displaying the first interface, the method also includes: at the tenth time point, displaying the eighth interface, the eighth interface including a first button for determining to set gesture navigation; in response to the operation on the first button, setting gesture navigation; at the eleventh time point, displaying the ninth interface, the ninth interface including a second button for completing the power-on wizard, the eleventh time point is later than the tenth time point; in response to the operation on the second button, at the twelfth time point, the terminal device starts the desktop application, the twelfth time point is later than the eleventh time point; at the thirteenth time point, the desktop application is started, and between the twelfth time point and the thirteenth time point, the desktop application is not started again, and between the twelfth time point and the thirteenth time point, the desktop application does not receive configuration change information sent by other modules.

[0274] The eighth interface may be the interface shown in b in FIG. 3 , the first button may be button 302 , the ninth interface may be the interface shown in c in FIG. 3 , the second button may be button 303 .

[0275] In response to the operation on the first button, the terminal device may execute the step shown in S404, and the system service initiates SendConfigChange() to the desktop application, but it is not actually executed. In response to the operation on the second button, the terminal device executes the steps shown in S503-S506, and determines not to initiate SendConfigChange() to the desktop application based on the configuration item.

[0276] Between the twelfth time point and the thirteenth time point, the desktop application was not started again and the interface application did not receive the configuration change information sent by other modules. It can be understood that since the system service determined not to initiate a sendconfigchange() command to the desktop application or to initiate a desktop application startup instruction based on the configuration item, the desktop application will not receive the sendconfigchange() command and will not be started again.

[0277] In one possible implementation, the terminal device is configured with a system service and a desktop application, and the desktop application is configured with configuration items. After the twelfth time point, the method also includes: the system service notifies the desktop application to start the desktop; the system service obtains the configuration of the desktop application from the desktop application; the system service includes the configuration items based on the configuration in the desktop application, and does not send configuration change information to the desktop application.

[0278] The method provided in the embodiment of the present application is described above in conjunction with Figures 3 to 10. The device for executing the above method provided in the embodiment of the present application is described below. As shown in Figure 11, Figure 11 is a structural schematic diagram of a desktop display device provided in the embodiment of the present application. The desktop display device can be a terminal device in the embodiment of the present application, or a chip or chip system within the terminal device.

[0279] As shown in FIG11 , a desktop display device 1100 can be used in a communication device, circuit, hardware component, or chip. The desktop display device 1100 includes a display unit 1101 and a processing unit 1102. The display unit 1101 is used to support the display step of the desktop display method; the processing unit 1102 is used to support the desktop display device 1100 in performing the information processing step.

[0280] In a possible implementation, the desktop display device 1100 may further include a communication unit 1103, and the communication unit 1103 is used to support the desktop display device 1100 in executing steps such as receiving or sending messages.

[0281] The desktop display devices described in the embodiments of the present application may include the units described in the embodiment corresponding to FIG. 11 .

[0282] Specifically, the processing unit 1102 and the display unit 1101 may be integrated together, and the processing unit 1102 and the display unit 1101 may communicate with each other.

[0283] In a possible implementation, the desktop display device 1100 may further include a storage unit 1104. The storage unit 1104 may include one or more memories, and the memories may be devices in one or more devices or circuits for storing programs or data.

[0284] The storage unit 1104 can exist independently and be connected to the processing unit 1102 via a communication bus. The storage unit 1104 can also be integrated with the processing unit 1102.

[0285] Taking the example of a chip or chip system in which the desktop display device 1100 can be a terminal device in an embodiment of the present application, the storage unit 1104 can store computer-executable instructions for the terminal device method, so that the processing unit 1102 executes the terminal device method in the above embodiment. The storage unit 1104 can be a register, a cache, or a random access memory (RAM), etc. The storage unit 1104 can be integrated with the processing unit 1102. The storage unit 1104 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions. The storage unit 1104 can be independent of the processing unit 1102.

[0286] In one possible implementation, the desktop display device 1100 may further include a communication unit 1103. The communication unit 1103 is configured to support interaction between the desktop display device 1100 and other devices. For example, when the desktop display device 1100 is a terminal device, the communication unit 1103 may be a communication interface or interface circuit. When the desktop display device 1100 is a chip or chip system within the terminal device, the communication unit 1103 may be a communication interface. For example, the communication interface may be an input / output interface, pin, or circuit.

[0287] The device of this embodiment can be used to execute the steps executed in the above method embodiment. Its implementation principles and technical effects are similar and will not be described in detail here.

[0288] FIG12 is a schematic diagram of the hardware structure of another terminal device provided in an embodiment of the present application.

[0289] The terminal device includes a processor 1201, a communication line 1204 and at least one communication interface (the communication interface 1203 is exemplarily used for explanation in FIG12 ).

[0290] The processor 1201 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0291] Communications link 1204 may include circuitry that transmits information between the aforementioned components.

[0292] The communication interface 1203 uses any transceiver or other device for communicating with other devices or communication networks, such as Ethernet, wireless local area networks (WLAN), etc.

[0293] Possibly, the terminal device may further include a memory 1202 .

[0294] The memory 1202 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may be independent and connected to the processor via a communication line 1204. The memory may also be integrated with the processor.

[0295] The memory 1202 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 1201. The processor 1201 is used to execute the computer-executable instructions stored in the memory 1202, thereby implementing the method provided by the embodiment of the present application.

[0296] Possibly, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, and the embodiments of the present application do not specifically limit this.

[0297] In a specific implementation, as an embodiment, the processor 1201 may include one or more CPUs, such as CPU0 and CPU1 in FIG12 .

[0298] In a specific implementation, as an embodiment, the terminal device may include multiple processors, such as processor 1201 and processor 1205 in Figure 12. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0299] In the above embodiment, the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product, wherein the computer program product may be pre-written in the memory or downloaded and installed in the memory in the form of software.

[0300] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. For example, available media can include magnetic media (e.g., floppy disk, hard disk or tape), optical media (e.g., digital versatile disc (DVD)), or semiconductor media (e.g., solid state disk (SSD)), etc.

[0301] The present application also provides a computer-readable storage medium. The methods described in the above embodiments can be implemented in whole or in part via software, hardware, firmware, or any combination thereof. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one location to another. The storage medium can be any target medium that can be accessed by a computer.

[0302] As one possible design, computer-readable media may include compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM or other optical disc storage; computer-readable media may include magnetic disk storage or other magnetic disk storage devices. Moreover, any connecting line may also be appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically using lasers.

[0303] The above combinations are also included within the scope of computer-readable media. The above are only specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

[0304] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

Claims

1. A desktop display method, characterized in that: Applied to a terminal device, the method comprises: At a first time point, a first interface is displayed, the first interface is a desktop, and the wallpaper of the first interface is a first image; At a second time point, displaying a second interface, the second interface including a thumbnail of a second image, the second time point being later than the first time point, and the posture of the terminal device not changing between the first time point and the second time point; In response to rotating the terminal device, at a third time point, displaying a third interface, the third interface is an interface obtained by rotating the second interface to fit the display screen, the third time point being later than the second time point; Based on the user's operation on the thumbnail of the second image on the third interface, at a fourth time point, setting the second image as a desktop wallpaper, the fourth time point being later than the third time point; In response to the user's operation of returning to the desktop, at a fifth time point, a fourth interface is displayed, and the fourth interface is an interface after the first interface is adapted to the rotation of the display screen and the wallpaper is changed to the second image. The fifth time point is later than the fourth time point. Between the third time point and the fourth time point, the desktop application is not started again. Between the fourth time point and the fifth time point, the desktop application does not receive configuration change information sent by other modules. Between the third time point and the fourth time point, the desktop application receives configuration change information.

2. The method according to claim 1, characterized in that The terminal device is a first device having an outward folding screen, the fourth interface is an interface displayed on a first screen of the outward folding screen, and after displaying the fourth interface, the method further includes: At a sixth time point, a fifth interface is displayed on the first screen, the fifth interface including a thumbnail of the first image, and the sixth time point is later than the fifth time point; In response to the operation of folding the first device, at a seventh time point, a sixth interface is displayed on the second screen, the sixth interface is an interface after the fifth interface is adapted to the display screen and folded, the second screen is a partial screen of the first screen, and the seventh time point is later than the sixth time point; Based on the user's operation on the thumbnail of the first image on the sixth interface, at an eighth time point, setting the first image as a desktop wallpaper, the eighth time point being later than the seventh time point; In response to the user's operation of returning to the desktop, at a ninth time point, a seventh interface is displayed, the seventh interface being the interface after the fourth interface is folded to adapt the display screen and the wallpaper is changed to the first image, the ninth time point is later than the eighth time point, between the seventh time point and the eighth time point, the desktop application is not started again, between the eighth time point and the ninth time point, the desktop application does not receive configuration change information sent by other modules, and between the seventh time point and the eighth time point, the desktop application receives configuration change information.

3. The method according to claim 1, characterized in that: The second interface includes a thumbnail of the first image, the thumbnail of the first image includes a selection mark, and the thumbnail of the second image does not include the selection mark.

4. The method according to any one of claims 1 to 3, characterized in that: The terminal device is configured with system services and desktop applications. After the terminal device is rotated, the method further comprises: the system service sends a Initiating a first instruction, the first instruction includes information for instructing screen rotation, and the type of the configchange object in the first instruction is a non-resource change type; After the user's operation on the thumbnail of the second image on the third interface, the method also includes: the system service initiates a second instruction to the desktop application, and the second instruction includes the information of the configuration change; the type of the configchange object in the second instruction is a resource change type, and the desktop application sets the first flag to true.

5. The method according to claim 4, characterized in that The desktop application sets the first flag to true, including: Based on the fact that the type of the configchange object in the second instruction is a resource change type, the desktop application sets the first flag to true.

6. The method according to claim 4 or 5, characterized in that: After responding to the user's operation of returning to the desktop, the method further includes: Based on the first flag being true, the desktop application obtains the configuration change information, and uses the configuration change information to display the fourth interface; After the desktop application obtains the information about the configuration change, the desktop application sets the first flag to false.

7. The method according to claim 6, characterized in that The desktop application is configured with configuration items. Before the desktop application obtains information about the configuration change, the method further includes: The system service notifies the desktop application to start the desktop; The system service obtains the configuration of the desktop application from the desktop application; The system service does not send the configuration change information to the desktop application based on the configuration in the desktop application including the configuration item.

8. The method according to any one of claims 1 to 7, characterized in that: Before displaying the first interface, the method further includes: At the tenth time point, an eighth interface is displayed, wherein the eighth interface includes a first button for determining to set the gesture navigation; In response to an operation on the first button, setting gesture navigation; At an eleventh time point, a ninth interface is displayed, wherein the ninth interface includes a second button for completing the startup wizard, and the eleventh time point is later than the tenth time point; In response to the operation on the second button, at a twelfth time point, the terminal device starts the desktop application, and the twelfth time point is later than the eleventh time point; At the thirteenth time point, the desktop application is started up, between the twelfth time point and the thirteenth time point, the desktop application is not started again, and between the twelfth time point and the thirteenth time point, the desktop application does not receive the configuration change information sent by other modules.

9. The method according to claim 8, characterized in that The terminal device is configured with a system service and a desktop application, and the desktop application is configured with a configuration item. After the twelfth time point, the method further includes: The system service notifies the desktop application to start the desktop; The system service obtains the configuration of the desktop application from the desktop application; The system service does not send the configuration change information to the desktop application based on the configuration in the desktop application including the configuration item.

10. A terminal device, characterized in that: include: processor and memory, wherein The memory is used to store computer programs; The processor is configured to call and execute the computer program so that the terminal device executes the method according to any one of claims 1 to 9.

11. A computer-readable storage medium, characterized in that: Used to store a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 9.

Images