Method and terminal device for loading desktop interface

Abstract

The present application discloses a method for loading a desktop interface and a terminal device, and relates to the field of terminal technology. After the terminal device is turned on or restarted, the first part of the elements of the desktop interface is loaded first, and the loading speed of the first part of the elements is relatively fast. After the first part of the elements of the desktop interface is loaded, the startup animation is triggered to stop playing; the terminal device displays the desktop interface. After the startup animation stops playing, the remaining elements of the desktop interface are loaded. After the remaining elements of the desktop interface are loaded, the terminal device refreshes and displays the desktop interface. Since the loading speed of the first part of the elements of the desktop interface is relatively fast, the time it takes for the terminal device to play the startup animation is shortened, which brings the user a faster startup or restart speed experience of the terminal device.

Description

Technical Field

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

[0002] Typically, a terminal device provides a desktop interface that displays information such as weather and date. It also displays application icons, which users can click to launch.

[0003] For example, after a terminal device successfully boots up, it can display the desktop interface. For example, after an application interface exits, the desktop interface can be displayed. In these scenarios, the terminal device loads the desktop interface, and once it loads successfully, it displays on the display. Controlling the desktop interface loading process on the terminal device to improve the user experience is a problem that needs to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a method and a terminal device for loading a desktop interface, which can improve the user experience of the terminal device during the process of loading the desktop interface.

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

[0006] In a first aspect, a method for loading a desktop interface is provided, the method comprising: after a terminal device is started, playing a startup animation; the terminal device begins loading a first portion of elements of the desktop interface; after the first portion of elements has been loaded, the terminal device stops playing the startup animation and displays the first portion of elements of the desktop interface; then the terminal device loads a second portion of elements of the desktop interface; after the second portion of elements has been loaded, the terminal device refreshes and displays the desktop interface; the refreshed desktop interface includes the first portion of elements and the second portion of elements. The desktop interface elements include control icons, application icons, and wallpaper; the second portion of elements are elements in the desktop interface other than the first portion of elements.

[0007] In this method, after the terminal device is turned on or restarted, the desktop interface is loaded in two stages. The first part of the desktop interface elements is loaded first, and the loading speed of the first part of the elements is faster. After the first part of the desktop interface elements is loaded, the startup animation is triggered to stop playing; the terminal device displays the desktop interface, and the displayed desktop interface includes the first part of the elements that have been loaded. After the startup animation stops playing, the second part of the desktop interface elements (the remaining elements) are loaded. After the second part of the desktop interface elements is loaded, the terminal device refreshes and displays the desktop interface, and the refreshed desktop interface includes the first part of the elements and the second part of the elements. In this way, after the first part of the desktop interface elements is loaded, the startup animation stops playing, and the terminal device displays the desktop interface. Compared with the method of exiting the startup animation after all the elements of the desktop interface are loaded, the first part of the desktop interface elements are loaded first in this method; the loading speed of the first part of the desktop interface elements is faster, which shortens the time it takes for the terminal device to play the startup animation, and brings the user a faster startup or restart speed experience of the terminal device.

[0008] In combination with the first aspect, in a possible implementation, the first part of elements includes at least one of a control icon and an application icon.

[0009] The control icons and application icons load faster. Loading the control icons and application icons first can shorten the time it takes for the terminal device to play the startup animation.

[0010] In one possible implementation, when the desktop interface includes a large number of application icons, a small number of application icons (e.g., the first row of application icons) are loaded first when the first portion of elements is loaded, and the remaining application icons are loaded when the second portion of elements is loaded. This can speed up the loading of the first portion of elements on the desktop interface and shorten the duration of the boot animation.

[0011] In combination with the first aspect, in a possible implementation, the second part of elements may include resources with a slow loading speed, such as wallpaper.

[0012] In combination with the first aspect, in a possible implementation, after the first part of the elements is loaded, the terminal device stops playing the boot animation, including: in response to the main thread of the desktop application being idle, the terminal device stops playing the boot animation; wherein, the desktop application is used to load the desktop interface.

[0013] In this method, the boot animation process monitors whether the main thread of the desktop application is idle. If the main thread of the desktop application is idle, it means that the first part of the elements has been loaded, and the animation stops playing.

[0014] In conjunction with the first aspect, in a possible implementation, in response to the main thread of the desktop application being idle, the terminal device loads the second part of the desktop interface elements. This ensures that the desktop interface is refreshed after the boot animation stops playing.

[0015] In combination with the first aspect, in a possible implementation, the terminal device loading the first part of elements of the desktop interface includes: if it is the first time that the desktop interface is loaded after the terminal device is started, the terminal device loads the first part of elements of the desktop interface.

[0016] If the terminal device is not booting up or restarting, for example, when a desktop application exits the foreground and returns to the foreground, since the resources of the loaded desktop interface elements have been saved when the desktop application exits the foreground, the first part of the elements will not be loaded again when the desktop application returns to the foreground, thus avoiding waste of system resources.

[0017] In combination with the first aspect, in a possible implementation, if the desktop interface is loaded for the first time after the terminal device is started, the terminal device loads the second part of elements of the desktop interface after stopping playing the startup animation.

[0018] If the device is not booting or restarting, for example, when a desktop application exits the foreground and then returns to the foreground, the resources for the loaded desktop interface elements have already been saved when the desktop application exits the foreground. When the desktop application returns to the foreground, all loaded elements have already been updated and displayed. Therefore, the second set of desktop interface elements is not loaded. This prevents screen flashing caused by refreshing the desktop interface after the normal display after the desktop application exits the foreground and then returns to the foreground.

[0019] In combination with the first aspect, in a possible implementation, the terminal device includes a power-on startup identifier, and the power-on startup identifier is a first value indicating that it is the first time the desktop interface is loaded after the terminal device is started, and the power-on startup identifier is a second value indicating that it is not the first time the desktop interface is loaded after the terminal device is started.

[0020] In a possible implementation, after the terminal device is started, the power-on flag is set to the first value; after the second part of elements is loaded, the power-on flag is set to the second value.

[0021] In a possible implementation, receiving an onCreate event of an activity corresponding to the desktop interface indicates that the terminal device is in the process of starting up or restarting, and the terminal device sets a startup flag to a first value.

[0022] In conjunction with the first aspect, in one possible implementation, after the terminal device is started, playing the boot animation includes: after the terminal device is started, starting a boot animation process; and the boot animation process starting to play the boot animation. The boot animation process also registers a listener with the AMS in the terminal device operating system to monitor when the main thread of the desktop application is idle. In this way, when the main thread of the desktop application is idle, the boot animation process can be promptly notified, triggering the cessation of the boot animation.

[0023] In a second aspect, a terminal device is provided, which has the functionality to implement the method described in the first aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functionality described above.

[0024] In a third aspect, a terminal device is provided, comprising: a processor, a display screen, and a memory; the memory is used to store computer execution instructions, and when the terminal device is running, the processor executes the computer execution instructions stored in the memory to enable the terminal device to execute a method as described in any one of the above-mentioned first aspects.

[0025] In a fourth aspect, a terminal device is provided, comprising: a processor; the processor is used to couple with a memory, and after reading instructions in the memory, execute the method as described in any one of the above-mentioned first aspects according to the instructions.

[0026] In a fifth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium. When the computer-readable storage medium is run on a computer, the computer can execute any one of the methods in the first aspect.

[0027] In a sixth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute any one of the methods described in the first aspect.

[0028] In a seventh aspect, a device (e.g., a chip system) is provided, comprising a processor for supporting a terminal device in implementing the functions described in the first aspect. In one possible design, the device further comprises a memory for storing program instructions and data necessary for the terminal device. When the device is a chip system, it may be composed of a chip or may include a chip and other discrete components.

[0029] Among them, the technical effects brought about by any design method in the second to seventh aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Figure 1A schematic diagram of a scenario example applicable to the method for loading a desktop interface provided in an embodiment of the present application;

[0031] Figure 2 A schematic diagram of a method for loading a desktop interface;

[0032] Figure 3 A schematic diagram of a scenario example of a method for loading a desktop interface;

[0033] Figure 4 A schematic diagram of a method for loading a desktop interface provided in an embodiment of the present application;

[0034] Figure 5 A schematic diagram of a scenario example of a method for loading a desktop interface provided in an embodiment of the present application;

[0035] Figure 6 A schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application;

[0036] Figure 7 A schematic diagram of a system architecture applicable to a method for loading a desktop interface provided in an embodiment of the present application;

[0037] Figure 8 A flowchart of a method for loading a desktop interface;

[0038] Figure 9 A flowchart of a method for loading a desktop interface provided in an embodiment of the present application;

[0039] Figure 10 A schematic diagram of a method for loading a desktop interface provided in an embodiment of the present application;

[0040] Figure 11 A flowchart of a method for loading a desktop interface provided in an embodiment of the present application;

[0041] Figure 12 A flowchart of a method for loading a desktop interface provided in an embodiment of the present application;

[0042] Figure 13 A schematic diagram of the structural composition of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: the situation where A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are a kind of "or" relationship.

[0044] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

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

[0046] After the terminal device is successfully started, the desktop interface can be displayed. The desktop interface can include various elements, for example, control icons, application icons, wallpapers, etc. For example, if the terminal device is a large screen, Figure 1As shown, large screen 100 displays desktop interface 101. Desktop interface 101 includes several control icons, such as a "Search" icon 102, a "Settings" icon 103, a "Wi-Fi" icon 104, and a "Time" icon 105. Among them, "Search" icon 102 is used for online search, "Settings" icon 103 is used to set various parameters of large screen 100, "Wi-Fi" icon 104 is used to set the Wi-Fi function, and "Time" icon 105 is used to display the current time. Desktop interface 101 also includes several application icons for launching corresponding applications, such as a "Shopping" icon 106, a "Short Video" icon 107, a "Karaoke" icon 108, a "Game" icon 109, a "Video" icon 10a, a "Music" icon 10b, application icons 10c, 10d, 10e, 10f, 10g, and 10h. Desktop interface 101 also includes wallpaper 10k.

[0047] In one scenario, a terminal device displays the desktop interface after it is powered on or restarted. Because it takes time for the terminal device to load various elements on the desktop interface, the terminal device generally plays a startup animation after powering on or restarting. Once the desktop interface loads successfully, the startup animation ends and the desktop interface is displayed.

[0048] In one implementation, Figure 2 As shown, after the terminal device is powered on or restarted, the boot animation starts. Then the desktop application starts, and the desktop interface begins loading. After all elements of the desktop interface are loaded and the desktop application is launched, the boot animation stops. When the boot animation stops, the desktop interface is displayed.

[0049] For example, Figure 3 As shown, the large screen 100 is powered on, and after the display screen is lit, a boot animation 110 is played. After the boot animation 110 plays for a period of time, the boot animation 110 is exited. The large screen 100 displays the desktop interface 101.

[0050] In this implementation, after the terminal device is powered on or restarted, it begins loading all elements of the desktop interface. Once all elements of the desktop interface are loaded, the desktop application is launched and the startup animation stops playing. The longer it takes to load all elements of the desktop interface, the longer it takes for the terminal device to play the startup animation, resulting in a slower startup experience for the user.

[0051] An embodiment of the present application provides a method for loading a desktop interface. After the terminal device is turned on or restarted, it starts to load a portion of the elements of the desktop interface; for example, the control icons, a portion of the application icons in the desktop interface, etc. After a portion of the elements of the desktop interface are loaded, the boot animation stops playing and the desktop interface is displayed. After the remaining elements of the desktop interface (for example, application icons that are not fully displayed in the desktop interface, wallpaper in the desktop interface, etc.) are loaded, the desktop interface is refreshed and displayed. Compared with loading all the elements of the desktop interface, loading a portion of the elements of the desktop interface takes less time, thus shortening the duration of playing the boot animation and giving the user a faster experience of booting up the terminal device.

[0052] In one implementation, Figure 4 As shown, after the terminal device is powered on or restarted, the boot animation starts. Then, the desktop application starts, and the desktop interface begins loading. A portion of the desktop interface elements are loaded first. After these elements are loaded, the boot animation stops, and the desktop interface is displayed. At this point, the desktop interface includes the loaded elements, but not the unloaded elements. The terminal device continues loading the remaining elements of the desktop interface. After the remaining elements are loaded, the desktop application starts, and the desktop interface is refreshed and displayed. At this point, the desktop interface includes all elements.

[0053] For example, Figure 5 As shown, the large screen 100 is powered on, and the display screen lights up and plays the boot animation 110. After the boot animation 110 plays for a period of time, it stops playing, and the large screen 100 displays the desktop interface. At this time, only the control icons and the first row of application icons of the desktop interface are loaded. Other application icons, wallpapers and other elements (remaining elements) have not yet been loaded. Figure 5As shown, after the boot animation 110 stops playing, the desktop interface displayed includes a "Search" icon 102, a "Settings" icon 103, a "Wi-Fi" icon 104, a "Time" icon 105, a "Shopping" icon 106, a "Short Video" icon 107, a "Karaoke" icon 108, a "Game" icon 109, a "Video" icon 10a, and a "Music" icon 10b. The large screen 100 continues to load the remaining elements of the desktop interface. After completing the loading of the remaining elements of the desktop interface, the desktop interface is refreshed and displayed. The refreshed desktop interface includes a "Search" icon 102, a "Settings" icon 103, a "Wi-Fi" icon 104, a "Time" icon 105, a "Shopping" icon 106, a "Short Video" icon 107, a "Karaoke" icon 108, a "Game" icon 109, a "Video" icon 10a, a "Music" icon 10b, an application icon 10c, an application icon 10d, an application icon 10e, an application icon 10f, an application icon 10g, an application icon 10h, and a wallpaper 10k. Generally speaking, wallpapers are large in size and loading them takes time. First, load the control icons and the first row of application icons on the desktop interface (without loading the wallpaper), then exit the boot animation and display the desktop interface, which can effectively shorten the boot animation display time.

[0054] The method provided in the embodiments of the present application can be applied to terminal devices including desktop interfaces. The above-mentioned terminal devices may include large screens, smart screens, smart TVs, mobile phones, tablet computers, laptops, personal computers (PCs), ultra-mobile personal computers (UMPCs), handheld computers, netbooks, smart home devices (such as smart speakers, smart air conditioners, etc.), personal digital assistants (PDAs), vehicle-mounted devices, virtual reality devices, etc., and the embodiments of the present application do not impose any restrictions on this.

[0055] In the embodiment of the present application, the terminal device is a terminal device that can run an operating system and install applications. Optionally, the operating system running on the terminal device can be system, system, System, etc.

[0056] Take the case where the terminal device is a large screen. Figure 6 1 shows a schematic diagram of the hardware structure of the large screen 100. Figure 6 As shown, the large screen 100 may include: a display screen 10, a processor 20, a memory 30, a power management module 40, an audio module 50, an indicator 60, a button 70, a camera 80, a wireless communication module 90, and multiple interfaces, etc.

[0057] For example, the multiple interfaces may include: a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, a network interface, an antenna interface, a video interface, an external memory interface, and the like.

[0058] It should be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the large screen 100. In other embodiments, the large screen 100 may include more or fewer components than shown, or may combine or separate certain components, or have different component arrangements. The components shown in the illustrations may be implemented in hardware, software, or a combination of software and hardware.

[0059] The memory 30 can be used to store computer executable program code, which includes instructions. The memory 30 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the large screen 100 (such as audio data, video data, playback records of audio / video data, etc.), etc. In addition, the memory 30 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 20 executes various functional methods or data processing of the large screen 100 by running instructions stored in the memory 30, and / or instructions stored in a memory provided in the processor 20.

[0060] The processor 20 may include one or more processing units. For example, the processor 20 may include an application processor (AP), a tuner / demodulator, a graphics processing unit (GPU), an image signal processor (ISP), a video processor, a controller, a digital signal processor (DSP), and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0061] The controller can be the nerve center and command center of the large screen 100. The controller can control the operation of the large screen 100 and respond to user operations through the operating system and various software control programs stored in the memory 30. The controller can control the overall operation of the large screen 100. For example, in response to receiving a user command to select a UI object in a graphical user interface (GUI) displayed on the display screen 10, the controller can execute an event related to the UI object selected by the user command.

[0062] For example, the user command for selecting a UI object may be a command inputted through various input devices (such as the control device 200, a mouse, a keyboard, a touchpad, etc.) connected to the large screen 100. Alternatively, the user command may be a user interaction gesture captured by the camera 80.

[0063] GUI is a commonly used form of user interface, which refers to a user interface related to computer operations that is displayed in a graphical manner. The user interface is a medium interface for interaction and information exchange between an application or operating system and a user, which realizes the conversion between the internal form of information and the form acceptable to the user. A UI object can be an interface element such as an icon, a window, a control, a hyperlink, etc. displayed on a display screen of an electronic device (such as a large screen 100), wherein a control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, etc. For example, when the UI object is a hyperlink, the event related to the UI object can be any of the following: displaying a hyperlink page, document, or image, etc. When the UI object is an icon, the event related to the UI object can be: executing the operation of the program corresponding to the icon.

[0064] The graphics processing unit (GPU) is used to generate various graphical objects, such as icons, operation menus, and graphics displayed in response to user input commands. The GPU may include an arithmetic unit for performing operations on various interactive commands input by the user. The GPU may also include a renderer for rendering the various UI objects generated by the arithmetic unit. These rendered UI objects are then displayed on the display screen 10. Of course, these GPU-processed UI objects may still need to be processed by the video processor before they can be finally displayed on the display screen 10.

[0065] The video processor can receive an external video signal and perform decompression, decoding, scaling, noise reduction, frame rate conversion, resolution conversion, image synthesis, and other processing on the external video signal according to the standard codec protocol of the external video signal to obtain a signal that can be directly displayed or played on the display screen 10 of the large screen 100. Exemplarily, the video processor may include a demultiplexing module, a video codec module, an image synthesis module, a frame rate conversion module, a display formatting module, and the like.

[0066] In some embodiments, the GPU and the video processor may be integrated or separately configured. When the GPU and the video processor are integrated, they may perform all image processing of the signals output to the display screen 10; when they are separately configured, they may each perform different functions.

[0067] In some embodiments, the processor 20 may further include an audio processor. Of course, the audio processor may also be provided independently of other processing units in the processor 20. For example, the audio processor may be Figure 6 The audio module 50 is shown. For a detailed description of the audio module 50, please refer to the content of the following embodiments, which will not be repeated here.

[0068] A tuner-demodulator receives broadcast television signals via wired or wireless means, performs demodulation processing such as amplification, mixing, and resonance on the broadcast television signals, and demodulates audio and video signals from multiple broadcast television signals. These audio and video signals may include television audio and video signals carried on the user's selected television channel frequency, as well as electronic program guide (EPG) data signals.

[0069] In some embodiments, the frequency demodulated by the tuner-demodulator is controlled by the processor 20 (e.g., a controller in the processor 20). The controller may send a control signal based on the frequency of the broadcast television signal selected by the user, so that the modem responds to the control signal and demodulates the broadcast television signal carried by the frequency selected by the user.

[0070] Broadcast television signals can be categorized as terrestrial broadcast signals, cable broadcast signals, satellite broadcast signals, or internet broadcast signals, depending on the broadcast format. Alternatively, they can be categorized as digital modulation signals, analog modulation signals, or the like, depending on the modulation type. Alternatively, they can be categorized as digital signals or analog signals, depending on the signal type.

[0071] In other embodiments, the tuner-demodulator can be provided independently of the processor 20. That is, the tuner-demodulator can be provided in an external device (such as an external set-top box) of the large screen 100. In this way, the external set-top box can demodulate the received broadcast television signal and then output the demodulated television audio and video signal to the large screen 100 via a wired or wireless connection between the external set-top box and the large screen 100.

[0072] The ISP is used to process data fed back by the camera 80. For example, the ISP can be used to process data collected by the camera 80 when the large screen 100 is making a video call. Specifically, light is transmitted through the lens to the camera's photosensitive element, and the light signal is converted into an electrical signal. The camera's photosensitive element transmits the electrical signal to the ISP for processing and converting it into an image visible to the naked eye. The ISP can also perform algorithmic optimization on image noise, brightness, and skin color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 80.

[0073] Processor 20 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 20 may be a cache memory. This memory can store instructions or data that have been used or are frequently used by processor 20. When processor 20 needs to use the instruction or data, it can directly access it from this memory. This avoids duplicate accesses, reduces processor 20 latency, and thus improves system efficiency.

[0074] In some embodiments, the processor 20 may include one or more interfaces. The interfaces of the processor 20 may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, etc. The processor 20 can be connected to the above-mentioned display screen 10, audio module 50, camera 80, wireless communication module 90 and other devices through at least one of the above interfaces. These interfaces in the processor 20 can also be used to realize the interconnection of various processing units in the processor 20 (such as AP, tuner demodulator, GPU, ISP, video processor, controller, etc.).

[0075] The power management module 40 is used to connect to an external power source, receive input from the external power source, and power various components of the large screen 100, such as the processor 20, display screen 10, and wireless communication module 90. In some embodiments, the power management module 40 can also be provided in the processor 20. Specifically, the power management module 40 is used to receive input from the external power source under the control of the processor 20 and provide power supply support for the large screen 100.

[0076] Large screen 100 can implement display functions through a GPU, display screen 10, and an application processor. The GPU is a microprocessor for image processing that connects display screen 10 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 20 may include one or more GPUs, which execute program instructions to generate or change display information.

[0077] In some embodiments, the display screen 10 can be used to receive image signals output by the processor 20 (such as a CPU or a GPU) and display video content, images, and a menu control interface.

[0078] The video content may be content from broadcast television. The video content may also be content from various broadcast signals received via wired or wireless communication protocols. Alternatively, the video content may also be various content received from a network server via a network communication protocol. Alternatively, the video content may also be content shared on the large screen 100 by other devices in a multi-screen interactive scenario. Alternatively, the video content may also be content input via an external memory interface.

[0079] The audio module 50 is used to decompress and decode externally input audio signals, as well as perform noise reduction, digital-to-analog conversion, and amplification processing to generate sound signals that can be played through the speaker. The audio module 50 is also used to process sound signals collected by the microphone, perform noise reduction and analog-to-digital conversion, and generate audio signals that can be output.

[0080] The camera 80 can be used to capture images of the external environment.

[0081] The wireless communication function of the large screen 100 can be implemented through an antenna and a wireless communication module 90. The wireless communication module 90 can provide wireless communication solutions including WLAN (such as Wi-Fi network), Bluetooth, frequency modulation (FM), near field communication (NFC), infrared, etc. applied to the large screen 100. For example, the wireless communication module 90 can include at least one of a Wi-Fi chip, a Bluetooth communication protocol chip, a wired Ethernet communication protocol chip, other network communication protocol chips or near field communication protocol chips, and an infrared receiver.

[0082] The wireless communication module 90 can be one or more devices that integrate at least one communication processing module. The wireless communication module 90 receives electromagnetic waves via an antenna, demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 20. The wireless communication module 90 can also receive signals to be transmitted from the processor 20, modulate and amplify them, and convert them into electromagnetic waves for radiation through the antenna. In some embodiments, the antenna of the large screen 100 is coupled to the wireless communication module 90, allowing the large screen 100 to communicate with the network and other smart devices through wireless communication technology.

[0083] The wireless communication module 90 can also enable the large screen 100 to receive control signals from a control device 200 (such as a remote control or mobile phone). In some embodiments, a user inputs a user command through the control device 200, such as a remote control or mobile phone, and the control device 200 can transmit a corresponding control signal to the large screen 100. The wireless communication module 90 can receive the control signal, and other components of the large screen 100 can respond to the control signal.

[0084] Usually, the large screen 100 is equipped with a remote control. The above-mentioned control device 200 can be the remote control, which is used to control the large screen 100. Among them, the remote control can receive the user's input operation instructions, and convert the operation instructions into instructions that the large screen 100 can recognize and respond to, and act as an intermediary for the interaction between the user and the large screen 100. For example, the user can operate the Home button (home button) on the remote control to return to the desktop, and the remote control can send the control instruction corresponding to the return to desktop operation to the large screen, and the large screen 100 responds to the return to desktop operation to switch the desktop interface. For example, the user can operate the volume plus and minus keys on the remote control to implement volume plus and minus operations, and the remote control can send the control instruction corresponding to the volume plus and minus operations to the large screen, and the large screen 100 responds to the volume plus and minus operations to adjust the volume.

[0085] For example, Figure 7 A schematic diagram of a system architecture applicable to the method for loading a desktop interface provided in an embodiment of the present application is shown. Figure 7As shown, the large screen includes desktop applications, and users can interact with the large screen through the desktop interface provided by the desktop application. For example, the user moves the position of the hotspot on the desktop interface by pressing the "up", "down", "left" or "right" button on the remote control, and then presses the "OK" button on the remote control to open the application (application, App) corresponding to the application icon at the hotspot. For example, the user controls the startup of the desktop application and the display of the desktop interface by pressing the "Home" button on the remote control. When the App is closed or exits the foreground, the desktop application can be called through the App entrance to switch the desktop application to the foreground. The desktop application can call the relevant modules of the Android framework for image display, video playback, wireless communication, etc. through the standard application program interface (API) provided by the operating system (OS). The desktop application can also call the TV interface provided by the OS to obtain broadcast and television playback content.

[0086] Optionally, desktop applications can interact with cloud servers, obtaining various information and interactive content, as well as network services such as video on demand and advertising. Cloud servers can be a single cluster or multiple clusters, encompassing one or more server types. Desktop applications can also interact with other Internet of Things (IoT) devices through cloud servers.

[0087] The following describes in detail the method for loading the desktop interface provided by the embodiment of the present application in conjunction with the accompanying drawings.

[0088] After the terminal device is powered on or restarted, the boot animation process (bootanimation) is started, and the terminal device starts playing the boot animation. Then the terminal device starts the desktop application, and the desktop application starts loading the desktop interface.

[0089] In one implementation, reference Figure 8 After the desktop application is started, all elements of the desktop interface are loaded. During the loading process, the main thread of the desktop application is occupied; after all elements of the desktop interface are loaded, the main thread of the desktop application is idle.

[0090] When the boot animation process determines that the main thread of the desktop application is idle, it stops playing the boot animation. After all elements of the desktop interface are loaded, the desktop interface is displayed.

[0091] In this implementation, loading all elements of the desktop interface is time-consuming, and the terminal device takes a long time to play the boot animation, which will give the user an experience of slow terminal device startup.

[0092] In another implementation, reference Figure 9 After the desktop application is started, the first set of elements on the desktop interface are loaded. During the loading process, the main thread of the desktop application is occupied. After the loading of the first set of elements on the desktop interface is completed, the main thread of the desktop application is idle.

[0093] When the boot animation process determines that the main thread of the desktop application is idle, it stops playing the boot animation. After stopping playing the boot animation, the desktop interface is displayed. The desktop interface includes a first part of elements. For example, the displayed desktop interface includes all control icons and / or multiple application icons (such as the first row of application icons).

[0094] The desktop application continues to load the second part of the desktop interface elements (the remaining elements except the first part). For example, the second part of the desktop interface elements includes wallpaper, multiple application icons (such as application icons other than the first row of application icons), etc. After the second part of the desktop interface elements are loaded, the desktop interface is refreshed and displayed. The refreshed desktop interface includes all elements.

[0095] refer to Figure 10 , Figure 10 (a) corresponds to Figure 8 The implementation shown. Figure 10 In the implementation shown in (a), after the desktop application is started, all elements of the desktop interface are loaded. After all elements of the desktop interface are loaded, the main thread of the desktop application is idle. If it is determined that the main thread of the desktop application is idle, the boot animation is stopped.

[0096] Figure 10 (b) corresponds to Figure 9 The implementation shown. Figure 10 In the implementation shown in (b), after the desktop application is started, the first part of the desktop interface elements are loaded first. After the first part of the desktop interface elements are loaded, the desktop application main thread is idle. When it is determined that the desktop application main thread is idle, the boot animation is stopped. Since the loading time of the first part of the desktop interface elements is shorter than the loading time of all the desktop interface elements, Figure 10 In the implementation shown in (b), the boot animation playback time is longer than Figure 10 In the implementation shown in (a), the boot animation playback duration is short.

[0097] use Figure 10 The implementation method shown in (b) loads the desktop interface, which can provide users with a faster terminal device startup experience.

[0098] The first part of the desktop interface elements may include elements with a faster loading speed, such as control icons and application icons; the second part of the elements may include elements with a slower loading speed, such as wallpaper. In one example, if there are a large number of application icons on the desktop interface, a small number of application icons (such as the first row of application icons) may be loaded when the first part of the elements is loaded, and the remaining application icons may be loaded when the second part of the elements is loaded.

[0099] Since the control icons and a small number of application icons on the desktop interface load quickly, the speed of loading the first part of the desktop interface elements can be accelerated, shortening the playback time of the boot animation.

[0100] In some embodiments, after the terminal device is turned on or restarted, the desktop application is started and the Activity corresponding to the desktop interface is created, that is, the onCreate event of the Activity corresponding to the desktop interface is executed to enter the life cycle of the Activity corresponding to the desktop interface.

[0101] The life cycle of an Activity includes onCreate, onStart, onResume, onPause, onStop, onRestart, and onDestroy.

[0102] onCreate: Executed when the Activity is first loaded. The onCreate event is executed when the interface is first launched. After the Activity is destroyed, the onCreate event is re-executed when it is reloaded.

[0103] onStart: Executed after the onCreate event. After exiting the interface and re-entering the interface after a period of time (the Activity is not destroyed), the onCreate event will be skipped and the onStart event will be executed directly.

[0104] onResume: Executed after the onStart event; or after the interface is swapped to the background, when the user views the interface again (the Activity has not been destroyed and the onStop event has not been executed), the onCreate and onStart events will be skipped and the onResume event will be executed directly.

[0105] onPause: Called when the interface is switched to the background.

[0106] onStop: Executed after the onPause event. If the user does not return to the screen within a certain period of time, the onStop event of the activity in that screen will be executed. Or if the user directly removes the screen from the current page, the onStop event of the activity in that screen will also be executed.

[0107] onRestart: After the onStop event is executed, if the interface and the application process are not destroyed by the system, the onRestart event of the activity of the interface will be executed when the user re-enters the interface. After the onRestart event, the onCreate event will be skipped and the onStart event will be executed directly.

[0108] onDestroy: Executed when the Activity is destroyed. After executing the onStop event, if you do not return to the interface again, the Activity will be destroyed.

[0109] The following describes in detail an implementation of the method for loading a desktop interface provided in an embodiment of the present application, in conjunction with the life cycle of the Activity corresponding to the desktop interface.

[0110] For example, Figure 11 As shown, the method for loading the desktop interface provided by the embodiment of the present application includes:

[0111] S201: After the terminal device is powered on or restarted, the boot animation process is started. The boot animation process calls the surface flinger to start playing the boot animation. The boot animation process also registers a listener with the AMS to monitor whether the main thread of the desktop application is idle.

[0112] S202: After the terminal device is powered on or restarted, the desktop application is started. The desktop application requests the AMS to create an activity corresponding to the desktop interface.

[0113] Activity management service (AMS) is a service in the terminal device operating system that is responsible for managing activities.

[0114] S203. The AMS triggers a creation (onCreate) event of the activity (Activity) corresponding to the desktop interface.

[0115] In one implementation, a startup flag is stored in the terminal device, and the startup flag is used to mark whether the desktop interface is loaded for the first time. Exemplarily, if the startup flag is a first value (for example, the startup flag is set to true), it indicates that the desktop interface is loaded for the first time, that is, the desktop interface is loaded during the terminal device startup or restart process; if the startup flag is a second value (for example, the startup flag is set to false), it indicates that the desktop interface is not loaded for the first time.

[0116] In one implementation, after receiving the onCreate event of the Activity corresponding to the desktop interface, the power-on flag is set to a first value; for example, the power-on flag is set to true.

[0117] For example, the boot flag is represented by mIsOnCreate. After receiving the onCreate event of the Activity corresponding to the desktop interface, the desktop application executes the code mIsOnCreate=true.

[0118] S204. The AMS triggers an onResume event of the activity corresponding to the desktop interface.

[0119] After the onCreate event, the onStart event is executed. After the onStart event, the onResume event of the Activity corresponding to the desktop interface is executed.

[0120] In one implementation, the AMS registers a listener with the desktop application to monitor whether the main thread of the desktop application is idle.

[0121] S205. The desktop application refreshes the loaded desktop interface elements.

[0122] The elements of the activity corresponding to the desktop interface are the elements of the desktop interface. The elements of the desktop interface can include control icons, application icons, wallpaper, etc. on the desktop interface.

[0123] Upon receiving the onResume event of the activity corresponding to the desktop interface, the desktop application refreshes the loaded desktop interface elements.

[0124] When the onResume event of the desktop interface activity is executed for the first time after the terminal device is powered on or restarted, the desktop interface has not yet been loaded and no loaded desktop interface elements exist.

[0125] After the desktop application loads the desktop interface, the desktop interface can be displayed on the display screen; the desktop interface displayed on the display screen includes the loaded desktop interface elements. When the desktop application exits the foreground, the resources of the loaded desktop interface elements will not be deleted. When the desktop application exits the foreground and returns to the foreground again, the resources of the loaded desktop interface elements are directly refreshed. For example, the desktop application is started, all elements of the desktop interface (control icons, application icons, wallpapers, etc.) have been loaded, and the terminal device displays the desktop interface. In response to user operations, another App is started, and the desktop application exits the foreground and enters the background; the resources of the loaded desktop interface elements will not be deleted. When the desktop application returns to the foreground again, the resources of the loaded desktop interface elements are directly refreshed, that is, the desktop interface elements have been loaded.

[0126] S206: If it is the first time to load the desktop interface (the boot flag is the first value), the desktop application loads the first part of elements of the desktop interface.

[0127] For example, when the value of mIsOnCreate is true, it indicates that the desktop interface is loaded for the first time, and the desktop application loads the first part of the desktop interface elements. The first part of the desktop interface elements may include:

[0128] S2061. The desktop application loads the control layout and control icons of the desktop interface.

[0129] S2062: The desktop application loads a preset number of application icons in the desktop interface.

[0130] Exemplarily, the preset number of application icons in the desktop interface is the first row of application icons on the desktop interface.

[0131] If the desktop interface is not loaded for the first time (not during the terminal device startup or restart process), for example, if the desktop application exits the foreground and then returns to the foreground, the first part of the desktop interface elements will not be loaded. Because the desktop application has refreshed the resources of the loaded desktop interface elements in S205, including the first part of the desktop interface elements, not loading the first part of the desktop interface elements can avoid repeatedly loading application icons in the desktop interface and wasting system resources.

[0132] S207: The desktop application calls a surface flinger to generate a desktop interface.

[0133] During the process of starting up or restarting the terminal device (loading the desktop interface for the first time), the desktop application loads the first part of the elements in the desktop interface, and the desktop interface generated by the surface compositor includes the first part of the elements. Figure 5Shown are a “Search” icon 102, a “Settings” icon 103, a “Wi-Fi” icon 104, a “Time” icon 105, a “Shopping” icon 106, a “Short Video” icon 107, a “Karaoke” icon 108, a “Game” icon 109, a “Video” icon 10a, and a “Music” icon 10b.

[0134] If the terminal device is not turned on or restarted, for example, when the desktop application exits the foreground and returns to the foreground, since the desktop application has refreshed the resources of the loaded desktop interface elements in S205, the desktop interface generated by the surface compositor includes all the elements of the desktop interface. Figure 1 The desktop interface is shown.

[0135] S208: The AMS detects that the main thread of the desktop application is idle, and notifies the boot animation process that the main thread of the desktop application is idle. The boot animation process stops playing the boot animation.

[0136] After the boot animation stops playing, the terminal device displays the desktop interface.

[0137] If it is the first time to load the desktop interface, S209-S210 are further executed; if it is not the first time to load the desktop interface, S209-S210 are not executed.

[0138] Exemplarily, when the value of mIsOnCreate is true, it indicates that the desktop interface is loaded for the first time, and S209 - S210 are executed.

[0139] In one implementation, after the desktop application determines that the main thread is idle, it triggers a determination as to whether the desktop interface is loaded for the first time. If it is the first time the desktop interface is loaded, S209-S210 are further executed; if it is not the first time the desktop interface is loaded, S209-S210 are not executed.

[0140] S209: The desktop application loads the second part of elements of the desktop interface.

[0141] The second part of the desktop interface is the elements of the desktop interface other than the first part. For example, the first part includes control icons and the first row of application icons; the second part includes application icons other than the first row of application icons, wallpaper, etc.

[0142] In one implementation, loading the second part of elements of the desktop interface may include S2091-S2092:

[0143] S2091. The desktop application loads application icons other than the first row of application icons in the desktop interface.

[0144] S2092. The desktop application loads the wallpaper of the desktop interface.

[0145] In one implementation, after the desktop application loads the second part of elements of the desktop interface, the boot flag is set to a second value; for example, the boot flag is set to false; that is, mIsOnCreate=false.

[0146] S210: The desktop application calls a surface flinger to refresh the desktop interface.

[0147] During the process of powering on or restarting the terminal device (loading the desktop interface for the first time), after loading the second part of the desktop interface elements, the desktop interface is refreshed and displayed. The refreshed desktop interface includes the second part of the desktop interface elements, that is, the refreshed desktop interface includes all elements. For example, the refreshed desktop interface includes Figure 5 Among them, there are "Search" icon 102, "Settings" icon 103, "Wi-Fi" icon 104, "Time" icon 105, "Shopping" icon 106, "Short Video" icon 107, "K Song" icon 108, "Game" icon 109, "Video" icon 10a, "Music" icon 10b, Application icon 10c, Application icon 10d, Application icon 10e, Application icon 10f, Application icon 10g, Application icon 10h, Wallpaper 10k, etc.

[0148] If the terminal device is not booting up or restarting (not loading the desktop interface for the first time), for example, if the desktop application exits the foreground and then returns to the foreground, the desktop application has already refreshed the resources of the loaded desktop interface elements in S205, and the desktop interface generated in S207 includes all the elements of the desktop interface. By not executing S209 and S210, it is possible to avoid screen flashing caused by refreshing the desktop interface again after the desktop application exits the foreground and then returns to the foreground.

[0149] After refreshing the desktop interface, the terminal device refreshes and displays the desktop interface.

[0150] Figure 12 A flowchart of a method for loading a desktop interface provided in an embodiment of the present application is shown.

[0151] For example, Figure 12 As shown, after the terminal device is powered on or restarted, the terminal device plays the boot animation. Afterwards, the terminal device starts the desktop application and sets the boot start flag to the first value, for example, mIsOnCreate=true, indicating that the desktop interface is loaded for the first time after the terminal device is powered on or restarted.

[0152] After the desktop application is launched, the terminal device begins loading the desktop interface. The terminal device refreshes the resources of previously loaded desktop interface elements. When the terminal device loads the desktop interface for the first time after powering on or restarting, the resources of previously loaded desktop interface elements do not exist.

[0153] The terminal device determines the value of the power-on startup identifier; if the power-on startup identifier is determined to be the first value, it is determined that this is the first time the desktop interface is loaded after the terminal device is powered on or restarted; if the power-on startup identifier is determined to be the second value, it is determined that this is not the first time the desktop interface is loaded after the terminal device is powered on or restarted.

[0154] When the terminal device loads the desktop interface for the first time after being powered on or restarted, the terminal device determines that the power-on startup flag is the first value and loads the first part of elements of the desktop interface.

[0155] After the first part of the desktop interface elements are loaded, the desktop application main process is idle, triggering the startup animation to stop playing. After the first part of the desktop interface elements are loaded, the terminal device displays the desktop interface, which includes the first part of the elements.

[0156] After the terminal device displays the desktop interface, the terminal device once again determines the value of the power-on startup identifier; if it is determined that the power-on startup identifier is the first value, it is determined that this is the first time the desktop interface is loaded after the terminal device is powered on or restarted; if it is determined that the power-on startup identifier is the second value, it is determined that this is not the first time the desktop interface is loaded after the terminal device is powered on or restarted.

[0157] When the terminal device loads the desktop interface for the first time after being powered on or restarted, the terminal device determines that the power-on startup identifier is the first value, loads the second part of the desktop interface elements (elements other than the first part), and sets the power-on startup identifier to the second value. The terminal device refreshes and displays the desktop interface. The refreshed desktop interface includes the first part of the desktop interface elements and the second part of the desktop interface elements, that is, the refreshed desktop interface includes all the elements of the desktop interface and is a complete desktop interface. After refreshing the desktop interface, the process of loading the desktop interface for the first time is completed.

[0158] In some embodiments, the desktop application will retreat to the background. For example, in response to a user operation, the first App is started, and the desktop application retreats to the background; the terminal device displays the user interface of the first App and stops displaying the desktop interface. After a period of time, the first App retreats to the background or is closed, the desktop application returns to the foreground, and the terminal device begins to load the desktop interface. The terminal device refreshes the resources of the desktop interface elements that have been loaded. When the desktop interface is loaded for the first time after the terminal device is turned on or restarted, the terminal device has already loaded all the elements of the desktop interface; when the desktop application returns to the foreground, all the elements of the desktop interface are refreshed.

[0159] Furthermore, the terminal device determines the value of the boot-up flag. When the desktop application returns to the foreground, the terminal device determines that the boot-up flag is the second value, determines that this is not the first time the desktop interface has been loaded since the terminal device was turned on or restarted, and does not load the first part of the desktop interface elements. The terminal device displays the desktop interface, which includes all elements of the desktop interface.

[0160] After the terminal device displays the desktop interface, it once again determines the value of the boot flag. When the desktop application returns to the foreground, the terminal device determines that the boot flag is the second value and that this is not the first time the desktop interface has been loaded since the terminal device was turned on or restarted. Therefore, the second part of the desktop interface elements is not loaded and the desktop interface is not refreshed.

[0161] The method for loading a desktop interface provided in an embodiment of the present application, when loading the desktop interface for the first time after a terminal device is powered on or restarted, performs loading in two stages. The first portion of the desktop interface elements is loaded first, and the loading speed of the first portion of the elements is relatively fast. After the loading of the first portion of the desktop interface elements is complete, the main thread of the desktop application is idle, triggering the cessation of the boot animation. The terminal device displays the desktop interface, which includes the first portion of the elements. Thereafter, the second portion of the desktop interface elements (the remaining elements) are loaded. In one implementation, the second portion of the elements may include resources that load more slowly, such as wallpaper. After the loading of the second portion of the desktop interface elements is complete, the terminal device refreshes and displays the desktop interface, which includes the first portion of the elements and the second portion of the elements. Thus, after the loading of the first portion of the desktop interface elements is complete, the boot animation stops and the terminal device displays the desktop interface. Compared to a method that exits the boot animation after all desktop interface elements are loaded, the method for loading a desktop interface provided in an embodiment of the present application loads the first portion of the desktop interface elements first. The faster loading speed of the first portion of the desktop interface elements shortens the duration of the boot animation playback on the terminal device, providing the user with a faster boot or restart experience on the terminal device.

[0162] It is understandable that the terminal device provided in the embodiment of the present application includes a hardware structure and / or software module for performing each function in order to realize the above functions. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiment disclosed herein, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiment of the present application.

[0163] The embodiment of the present application can divide the functional modules of the terminal device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0164] In one example, see Figure 13 , which shows a possible structural diagram of the terminal device involved in the above embodiment. The terminal device 1300 includes: a processing unit 1310, a storage unit 1320 and a display unit 1330.

[0165] The processing unit 1310 is configured to control and manage actions of the terminal device 1300, for example, loading the first part of elements of the desktop interface, loading the second part of elements of the desktop interface, and so on.

[0166] The storage unit 1320 is used to store program codes and data of the terminal device 1300. For example, it stores resources of the loaded desktop interface.

[0167] The display unit 1330 is used to display the interface of the terminal device 1300. For example, it can display the desktop interface.

[0168] Of course, the unit modules in the terminal device 1300 include but are not limited to the processing unit 1310, storage unit 1320 and display unit 1330. For example, the terminal device 1300 may further include a communication unit for supporting the terminal device 1300 to communicate with other devices.

[0169] The processing unit 1310 may be a processor or controller, such as a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The storage unit 1320 may be a memory. The display unit 1330 may be a display screen, etc. The communication unit may include a wireless communication unit.

[0170] For example, the processing unit 1310 is a processor (such as Figure 6The processor 20 shown in FIG. 13 ), the storage unit 1320 may be a memory (such as Figure 6 The memory 30 shown in FIG. 1 ), the display unit 1330 may be a display screen (such as Figure 6 The communication unit may be a wireless communication unit (such as a display screen 10 shown in FIG. Figure 6 The wireless communication module 90 shown). The terminal device 1300 provided in the embodiment of the present application can be Figure 6 The large screen 100 shown in FIG. The processor, memory, display screen, wireless communication unit, etc. can be connected together, for example, via a bus.

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

[0172] An embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned electronic device, the electronic device executes the various functions or steps executed by the mobile phone in the above-mentioned method embodiment.

[0173] The embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the functions or steps executed by the mobile phone in the above method embodiment.

[0174] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0175] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules or units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0176] The units described as separate components may or may not be physically separate, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0177] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0178] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0179] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for loading a desktop interface, applied to a terminal device, characterized in that: The method comprises: After the terminal device is started, the boot animation process is started and the desktop application is started; The boot animation process calls the surface synthesizer to start playing the boot animation; The desktop application triggers a creation event of an activity corresponding to the desktop interface; After executing a start event of an activity corresponding to the desktop interface, the desktop application loads a first portion of elements of the desktop interface; the first portion of elements includes at least one of a control icon and an application icon; wherein, during the process of the desktop application loading the first portion of elements, the main thread of the desktop application is occupied; The desktop application calls the surface synthesizer to generate a desktop interface; the desktop interface includes the first part of elements; After determining that the main thread of the desktop application is idle, the boot animation process stops playing the boot animation, and the terminal device displays the desktop interface; After determining that the main thread of the desktop application is idle, the desktop application loads a second part of elements of the desktop interface; the second part of elements includes wallpaper; The desktop application calls the surface synthesizer to refresh the desktop interface; The terminal device displays a refreshed desktop interface; the refreshed desktop interface includes the first part of elements and the second part of elements.

2. The method according to claim 1, characterized in that The first part of elements includes a preset number of application icons, and the second part of elements includes application icons other than the preset number of application icons in the desktop interface.

3. The method according to claim 1 or 2, characterized in that Before the desktop application loads the first part of elements of the desktop interface, the method further includes: Make sure that this is the first time the desktop interface is loaded after the terminal device is started.

4. The method according to claim 3, characterized in that Before the desktop application loads the second part of elements of the desktop interface, the method further includes: Make sure that this is the first time the desktop interface is loaded after the terminal device is started.

5. The method according to claim 3, characterized in that The terminal device includes a power-on start flag, wherein the power-on start flag having a first value indicates that the desktop interface is loaded for the first time after the terminal device is started, and the power-on start flag having a second value indicates that the desktop interface is not loaded for the first time after the terminal device is started.

6. The method according to claim 5, characterized in that The method further comprises: After the terminal device is started, the power-on start flag is set to a first value; After the second part of elements is loaded, the power-on flag is set to a second value.

7. The method according to claim 6, characterized in that After the terminal device is started, setting the power-on startup flag to the first value includes: In response to a creation event of an activity corresponding to the desktop interface, the terminal device sets the power-on flag to a first value.

8. The method according to claim 1 or 2, characterized in that After the boot animation process starts playing the boot animation, the method further includes: The boot animation process registers a monitor with the activity management service AMS in the terminal device operating system to monitor that the main thread of the desktop application is idle.

9. A terminal device, characterized in that: include: processor, display, and memory; One or more computer programs are stored in the memory. The one or more computer programs include instructions. When the instructions are executed by the terminal device, the terminal device executes the method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that The method comprises computer instructions; when the computer instructions are executed on an electronic device, the electronic device executes the method according to any one of claims 1 to 8.

Images