Method for displaying multitask animation and electronic device

Abstract

This application discloses a method for displaying multitasking animations and an electronic device, relating to the field of terminal technology. The method includes: the electronic device responding to clicking a preset icon to enter a multitasking scheduling mode and display a second interface; then, responding to a first operation input by the user on the second interface, displaying a first window of a first application; and responding to a second operation of swiping up from the bottom and pausing, displaying a multitasking animation (i.e., the recents animation). Each frame of the recents animation includes a window background and the display content of the first window; the display content of the first window is displayed on top of the window background. Since the content of the window background remains unchanged during the display of the recents animation, it means that the background of the multitasking cards used to display the content of the first application in the recents animation remains unchanged, solving the problem of jumps in the multitasking cards during the recents animation. This avoids the flickering problem of the recents animation and ensures the smooth playback of the recents animation.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method for displaying multi-tasking animation and an electronic device. Background Technology

[0002] Currently, electronic devices use Android. TM The system supports a multi-task scheduling mode. In this mode, in response to an action triggering any application, the electronic device displays a small window (e.g., a floating window) of that application. The size of this small window is smaller than the display area on the screen. This application can be referred to as the foreground application. While displaying the small window of the foreground application, the electronic device can also play the "recents" animation in response to user input triggering a multi-task animation. Each frame of the "recents" animation can include a task card corresponding to the foreground application. The task card for the foreground application is used to display the display status of the foreground application on the screen. This task card includes not only the content displayed in the small window of the foreground application but also the background image of the small window on the screen (which can be referred to as the background image).

[0003] One issue is that during the playback of the recents animation, the background image of the corresponding task card in the foreground changes, causing a visual jump in the task card. This, in turn, causes the recents animation to flicker, resulting in an unsmooth user experience. Summary of the Invention

[0004] This application provides a method and electronic device for displaying multi-task animations, which can solve the problem of task cards jumping in recent animations, thereby avoiding the flickering problem of recent animations, ensuring the smooth playback of recent animations, and bringing users a better visual experience.

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

[0006] In a first aspect, a method for displaying a recents animation is provided, the method comprising: displaying a first interface; the first interface comprising at least one first-type icon within a preset area and at least one second-type icon outside the preset area, the at least one first-type icon comprising a preset icon; in the first interface, in response to clicking the preset icon, displaying a second interface; the second interface comprising a preset area but excluding at least one second-type icon; then, in the second interface, in response to a first operation on the first icon in the preset area, displaying a first window of a first application, the size of the first window being smaller than the size of the display area; and further in response to a second operation of swiping up from the bottom and pausing, displaying the recents animation.

[0007] Each frame of the recents animation includes the window background and the content displayed in the first window; the content displayed in the first window is displayed on top of the window background; the size of the window background is equal to the size of the display area; during the display of the recents animation, the size of the window background decreases while the content of the window background remains unchanged.

[0008] Understandably, each frame of the "Recents" animation includes the window background. During the animation, the size of the window background decreases, indicating that it's not the desktop background. The content of the first application's first window is continuously displayed on the window background throughout the animation, ensuring a consistent view of the first application's window on the screen. Because the window background content remains unchanged during the animation, the background of the multitasking cards displaying the first application's content also remains constant, resolving the issue of jumps in multitasking card transitions. This avoids flickering in the "Recents" animation, ensuring smooth playback and providing a better visual experience for the user.

[0009] In conjunction with the first aspect, in one possible implementation, the window background and the content displayed in the first window change synchronously during the display of the recents animation; wherein, the synchronous change of the window background and the content displayed in the first window includes: the size of the window background and the size of the content displayed in the first window are scaled synchronously, and the position of the window background and the position of the content displayed in the first window are moved synchronously.

[0010] Understandably, during the display of the recents animation, the window background changes along with the content displayed in the first window, ensuring that the content of the first window is continuously displayed on the window background. This allows for a continuous display of the first application's first window's status within the display area.

[0011] In conjunction with the first aspect, another possible implementation method includes the following animations: the follow animation, the end animation, and the end screen; the second operation includes: the press operation, the slide operation, and the release operation after a pause.

[0012] The aforementioned response to the second operation of swiping up from the bottom and pausing, displaying the recents animation, includes: in response to the press operation, creating a blank background layer and a layer of the first application; the size of the background layer is equal to the size of the display area; the layer of the first application includes the display content of the first window; in response to the swipe operation, updating the background layer and the layer of the first application, and generating each image frame in the follow animation based on the updated background layer and the updated layer of the first application; the window background in each image frame of the follow animation displays the background layer; in response to the release operation after the pause, continuing to update the background layer and the layer of the first application, and generating each image frame in the end animation based on the updated background layer and the updated layer of the first application; the window background in each image frame of the end animation displays the background layer; based on the updated layer of the first application, generating the end screen; the window background in the end screen does not display the background layer.

[0013] Understandably, the tablet computer does not display a background layer in the end animation. This avoids the change in the window background in the end screen caused by displaying both a background layer and a background view simultaneously. This also avoids the visual jump in the multitasking card caused by the change in the window background in the recents animation.

[0014] In conjunction with the first aspect, another possible implementation involves generating the ending screen based on the updated first application's layer, which includes: triggering the drawing of a background view when the ending animation ends, and monitoring the drawing process of the background view; the size of the background view being equal to the size of the background layer in the last image frame of the ending animation; triggering the hiding of the background layer or triggering the destruction of the background layer when the background view is drawn; generating the ending screen based on the background view and the updated first application's layer; and displaying the background view in the window background of the ending screen, without displaying the background layer.

[0015] The tablet computer can trigger the drawing of all foreground visible task views after the animation ends, and monitor the drawing process of these task views. Drawing the task view may include drawing the background view. Monitoring the drawing process of the background view can refer to monitoring the drawing process of the task view. The completion of the background view drawing can refer to the completion of the drawing of the task view.

[0016] Understandably, by monitoring the drawing of all visible taskviews in real time (or detecting the drawing of background views), tablets can accurately determine when a taskview is finished drawing. This allows them to hide the background layer at the moment the taskview finishes drawing, or hide it beforehand. This avoids the issue of the window background changing due to the simultaneous display of the background layer and the background view in the taskview during the closing screen. Consequently, it avoids the visual jump between multitasking cards caused by changes in the window background during the recent animation, resolving the flickering issue in the recent animation and ensuring its smooth playback, thus providing a better visual experience for the user.

[0017] In conjunction with the first aspect, another possible implementation involves both the background layer and the background view being semi-transparent.

[0018] Understandably, the entire background layer can be semi-transparent; or, a portion of the background layer can be semi-transparent, while another portion can be transparent or solid. Similarly, the color of the background view can be similar to the color of the background layer.

[0019] In conjunction with the first aspect, in another possible implementation, before displaying the recents animation in response to the second operation of swiping up from the bottom and pausing, the method further includes: in the second interface, in response to a third operation on the second icon in a preset area, displaying a second window of the second application, the size of the second window being smaller than the size of the display area; wherein each image frame of the recents animation also includes the display content of the second window; the display content of the second window is displayed on top of the window background; during the display of the recents animation, the window background, the display content of the first window, and the display content of the second window all change synchronously.

[0020] Understandably, a tablet can display multiple application windows when entering multitasking mode, which may include a first window of a first application and a second window of a second application. In each frame of the recents animation, these multiple application windows are now displayed on top of the window background, demonstrating the display status of the multiple application windows on the display area.

[0021] In conjunction with the first aspect, another possible implementation method further includes: running a third application in the background, with the third application's third window being invisible. Each frame of the recents animation also includes the display content of the third window, the size of which is equal to the size of the display area; the display content of the third window does not overlap with the window background.

[0022] Understandably, because the window size of applications displayed on a tablet in multitasking mode (or foreground applications) is smaller than the display area, each frame in the recents animation includes not only the content displayed in the foreground application window but also the window background. Displaying the content of the foreground application window on the window background demonstrates its display status within the display area. However, for background applications, tablets typically display them in full-screen mode before exiting, so the background application window size is equal to the display area. Directly displaying the content of the background application window in each frame of the recents animation demonstrates its display status within the display area.

[0023] In a second aspect, an electronic device is provided, comprising: a processor, a memory, and a communication interface. The memory and the communication interface are coupled to the processor. The memory stores computer program code, including computer instructions. When the processor executes the computer instructions, the electronic device performs the multi-tasking animation display method as described in any one of the first aspects above.

[0024] Thirdly, a computer-readable storage medium is provided that stores computer instructions. When the computer instructions are executed on an electronic device, the electronic device causes the electronic device to perform the multitasking animation display method as described in any one of the first aspects above.

[0025] Fourthly, a computer program product containing computer instructions is provided, which, when executed on an electronic device, causes the electronic device to perform a method for displaying multitasking animation as described in any one of the first aspects above.

[0026] Fifthly, an apparatus (e.g., a chip system) is provided, comprising a processor for supporting an electronic device in implementing the multitasking animation display method described in the first aspect. In one possible design, the apparatus further comprises a memory for storing necessary program instructions and data of the electronic device. When the apparatus is a chip system, it may be composed of chips or may include chips and other discrete components.

[0027] The technical effects of any of the design methods in aspects two through five can be found in the technical effects of different design methods in aspect one, and will not be repeated here. Attached Figure Description

[0028] Figure 1(a) to (b) are schematic diagrams of the interface for entering and exiting a multi-task scheduling mode on a tablet computer according to an embodiment of this application;

[0029] Figure 2 (a) to (d) are schematic diagrams of the interface for launching the recents animation on a tablet computer in multi-task scheduling mode according to the embodiments of this application;

[0030] Figure 3 (a) to (d) are schematic diagrams of the interface for launching the recents animation on a tablet computer in multi-task scheduling mode, as provided in the embodiments of this application.

[0031] Figure 4 (a) to (b) are schematic diagrams of an interface for displaying a background application in a recents animation provided in the embodiments of this application;

[0032] Figure 5 (a) is a schematic diagram of background changes for a multi-task card in a recents animation provided by the prior art;

[0033] Figure 5 (b) is a schematic diagram of the background change of a multi-task card in a recents animation provided in an embodiment of this application;

[0034] Figure 6 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0035] Figure 7 A system architecture diagram of the electronic device provided in the embodiments of this application;

[0036] Figure 8 A flowchart illustrating a method for displaying multi-task animation provided in this application embodiment. Figure 1 ;

[0037] Figure 9 (a) in the figure is a schematic diagram of multiple stages in a recents animation provided by the prior art;

[0038] Figure 9 (b) is a schematic diagram of multiple stages in a recents animation provided in an embodiment of this application;

[0039] Figure 10 A schematic diagram illustrating the display content of multiple stages in another recents animation provided in an embodiment of this application;

[0040] Figure 11 A flowchart illustrating a method for displaying multi-task animation provided in this application embodiment. Figure 2 ;

[0041] Figure 12 A flowchart illustrating a method for displaying multi-task animation provided in this application embodiment. Figure 3 ;

[0042] Figure 13 A flowchart illustrating a method for displaying multi-task animation provided in this application embodiment. Figure 4 ;

[0043] Figure 14 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0044] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that “ / ” means “or,” for example, A / B can mean A or B; “and / or” in the text is merely a description of the relationship between related objects, indicating that three relationships can exist, for example, A and / or B can mean: A alone, A and B simultaneously, and B alone.

[0045] In this application, the reference to "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described in this application can be combined with other embodiments.

[0046] The terms "first" and "second" in the following embodiments of this application are for descriptive purposes only and should not be construed as implying relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0047] Before introducing the embodiments of this application, firstly, in conjunction with Figure 1 , Figure 2 , Figure 3 and Figure 4 The application scenarios of the embodiments of this application will be described. Among them, Figure 1 , Figure 2 , Figure 3 and Figure 4The examples used in this paper are tablet computers.

[0048] Reference Figure 1 The image shown is a schematic diagram of an interface for entering and exiting a multi-task scheduling mode on a tablet computer, according to an embodiment of this application. Figure 1 As shown in (a), the tablet computer displays a desktop interface 100, which may include a Dock area 110 for quick access to frequently used applications, folders, or settings options. Optionally, an application may also be referred to as an application (APP). The Dock area 110 may be located at the bottom or side of the display area, for example, Figure 1 The Dock area 110 shown in (a) is located at the bottom of the display area. The Dock area 110 can also be divided into two areas, for example, Figure 1 The left and right areas are shown in (a) above. The difference between these two areas lies in the content they contain. Generally, the left Dock displays icons of user-pinned applications, allowing users to quickly access frequently used applications; the right Dock may display system settings options, notifications, or other shortcuts for quickly switching settings or viewing relevant information.

[0049] like Figure 1 As shown in (a), the Dock area 110 includes not only application icons but also a multitasking icon 111 corresponding to the multitasking scheduling mode. Users can control the tablet to enter or exit multitasking scheduling mode by manipulating the multitasking icon 111, and the multitasking icon 111 displays differently when the tablet is in or out of multitasking scheduling mode. In some examples, Figure 1 The color of the multitasking icon 111 displayed when the tablet computer exits multitasking mode, as shown in (a) in the image, is similar to... Figure 1 The multitasking icon 111 displayed by the tablet computer in (b) is a different color when it enters multitasking mode. Optionally, multitasking mode can also be called free screen scheduling mode.

[0050] It should be noted that the multitasking icon (111) displayed on the tablet differs depending on whether it's in multitasking mode or not. This difference may include not only different colors but also variations in line thickness. Secondly, Figure 1 The multitasking icon 111 shown in (a) is merely an example. Other controls (e.g., switches or buttons) different from the icon can also be used to control the tablet computer to enter or exit the multitasking scheduling mode. This application embodiment does not limit this.

[0051] In this embodiment, the multi-task scheduling mode allows the display screen to simultaneously show windows of multiple applications, and the window sizes of all applications are smaller than the display area. Optionally, since the application windows displayed in multi-task scheduling mode are smaller than the display area, these application windows can be referred to as small windows. Furthermore, the small windows of the multiple applications displayed under the multi-task scheduling module are all interactive.

[0052] like Figure 1 As shown in (b), the tablet computer can receive and respond to user input by clicking the multitasking icon 111 when displaying the desktop interface 100, entering or activating the multitasking scheduling mode. Optionally, the tablet computer can configure some applications on the tablet to be launched in the multitasking scheduling mode. For example, the tablet computer can configure applications located in the Dock area 110 to be allowed to be launched in the multitasking scheduling mode. In this case, in response to clicking the multitasking icon 111, the tablet computer can not only enter the multitasking scheduling mode but also hide the icons of applications located outside the Dock area 110. Figure 1 As shown in (b), the icons of applications located outside the Dock area 110 on the desktop interface 100 are hidden and not visible.

[0053] Reference Figure 2 The image shown is a schematic diagram of the interface for launching the recents animation on a tablet computer in a multi-task scheduling mode, according to an embodiment of this application. Figure 2 As shown in (a), after the tablet enters multitasking mode, it displays Dock 110. The tablet can then receive and respond to the user clicking the icon of any application in Dock 110, displaying the application's window and hiding Dock 110. For example, as... Figure 2 As shown in (b), the tablet computer displays a small window 121 of application A.

[0054] In some examples, when a tablet responds to clicking the icon of any application in the Dock 110, displaying a small window for that application may include displaying the application as a floating window. A floating window is a small window that floats above the display area, typically appearing above other applications or the desktop interface. Floating windows can be moved and resized freely, allowing users to easily view or manipulate their content while performing other tasks.

[0055] When a tablet displays a small window of an application in multitasking mode, it can accept user input by swiping up from the bottom and pausing. For example, the trajectory of a swipe-up-from-the-bottom-and-pause action might look like this... Figure 2As shown by the dashed line in (b), the trajectory of this operation involves the user pressing at the starting point 131 of the dashed line, then swiping along the direction indicated by the arrow on the dashed line, and pausing at the ending point 132 of the dashed line. The swipe-up and pause operation triggers the tablet's multitasking management function (or the recents function), which displays the user's most recently opened tasks (or recently opened applications) so that the user can quickly switch to or revisit previously opened applications. To achieve a smooth display of the user's most recently opened applications, the tablet displays a recents animation in response to the swipe-up and pause operation. The recents animation provides a smooth display of the user's most recently opened applications, improving the user experience.

[0056] The swipe-up-and-pause action can include multiple operations, which, in the order of input, are a press (or down) operation, a swipe (or move) operation, and a lift-up (or up) operation. A down operation can refer to the user pressing the starting point 131. An up operation can refer to the user lifting their hand after touching the screen, and the user inputting the up operation after pausing at the endpoint 132. Furthermore, combining the multiple operations derived from the swipe-up-and-pause action, the recents animation can be divided into multiple stages, which, in the order of playback time, are a follow-up animation, an ending animation upon entering the multitasking management interface, and an ending screen.

[0057] Based on the above, the tablet computer's response to a swipe-up from the bottom and pause operation to display the "recents" animation may include: displaying a follow-up animation within the "recents" animation in response to a "move" operation; and displaying an ending animation within the "recents" animation in response to an "up" operation, followed by the final frame of the "recents" animation. The last image frame in this ending animation may be a multitasking management interface.

[0058] It's important to note that when the ending animation in the "Recents" animation finishes, the user visually perceives the "Recents" animation as over. However, on tablets, the end of the ending animation does not necessarily mean the end of the "Recents" animation; the tablet will display an ending screen after the ending animation. This ending screen can be the same as the multitasking interface.

[0059] For example, such as Figure 2 As shown in (c), the tablet responds to any move action in the swipe-up-and-pause operation by displaying an image frame from the haptic animation; then, as... Figure 2 As shown in (d), after the follow animation, the tablet displays the multitasking management interface 140 from the end animation.

[0060] Reference Figure 3 The diagram illustrates another interface for launching the recents animation on a tablet computer in multi-tasking mode, according to an embodiment of this application. In multi-tasking mode, the tablet computer can simultaneously display multiple application windows. Specifically, the process may include: after displaying application A's window 121 and hiding the Dock area 110, the tablet computer can receive and respond to a user's input of swiping up from the bottom, displaying the Dock area 110; then, it receives and responds to clicking the icon of another application in the Dock area 110, displaying the window of application A and the window of the other application. Furthermore, after the user clicks the icons of multiple applications in the Dock area 110, the tablet computer can display the windows of these multiple applications. Figure 3 As shown in (b), the multiple application windows displayed on the tablet computer may include: application A window 121, application B window 122, application C window 123, and application D window 124.

[0061] When a tablet displays multiple small windows of applications simultaneously, it can receive and respond to a swipe-up gesture from the bottom and pause, displaying a "recents" animation. For example, as... Figure 3 As shown in (c), the tablet responds to any move action in the swipe-up-and-pause operation by displaying an image frame from the haptic animation; then, as... Figure 3 As shown in (d), after the follow animation, the tablet displays the multitasking management interface 150 from the end animation.

[0062] It should be noted that the tablet computer displays... Figure 3 The interface shown in (a) is displayed. Figure 3 Other interfaces are also displayed between the interfaces shown in (b) above. Figure 3 Not shown in the image.

[0063] In this embodiment, regardless of the stage of the recents animation, each image frame in the recents animation (e.g., each image frame in the follow animation, each image frame in the end animation, the end screen) may include: a task card for displaying recently opened applications. Each task card corresponds to one or more recently opened applications. In the recents animation, all task cards typically undergo scaling and movement animation effects. For example, Figure 2 Task card 141 shown in (c) changes as follows: Figure 2 Task card 141 is shown in (d) in the diagram; for example, Figure 3 Task card 151 shown in (c) changes as follows: Figure 3Task card 151 is shown in (d) in the image. At the end of the recents animation, the positions of all task cards are fixed, and the user can switch to the application corresponding to any task card by clicking on it. For example, Figure 2 The position of task card 141 in the multitasking management interface 140 shown in (d) is fixed, and the position of task card 141 in the end screen displayed after the multitasking management interface 140 is also fixed. For example, Figure 3 The position of the task card 151 in the multitasking management interface 150 shown in (d) is fixed, and the position of the task card 151 in the end screen displayed after the multitasking management interface 150 is also fixed.

[0064] Recently opened applications refer to applications currently running on the tablet. Running applications can be categorized into background applications (or background apps) and foreground applications. Foreground applications can be further divided into interactive and non-interactive applications. Background applications are both invisible and non-interactive. Applications launched by the tablet in multitasking mode are foreground applications that are both visible and interactive, for example... Figure 2 Application A is shown in (b) above. Figure 3 Applications A, B, C, and D are shown in (b) above. Optionally, applications launched by the tablet in multitasking mode can be called foreground visible applications, and the task cards corresponding to the foreground visible applications can be called multitasking cards.

[0065] It should be noted that, Figure 2 (c) and (d) in the middle, and Figure 3 In (c) and (d), the task card corresponding to the background application is not shown.

[0066] In some embodiments, whether one application corresponds to one task card or multiple applications correspond to one task card may depend on whether the multiple applications are simultaneously closed or exited before the recents animation is displayed. If any single application is closed or exited individually, then that application corresponds to a separate task card. For example, as Figure 2 As shown in (b), when the tablet displays a small window of a foreground application, it receives and responds to a swipe-up and pause operation from the bottom, and the foreground application is exited individually; at this time, this one foreground application corresponds to a single task card 141. If multiple applications are closed or exited simultaneously, these multiple applications correspond to the same task card, for example, as shown in (b). Figure 3 As shown in (b), when the tablet displays small windows of multiple foreground visible applications, it receives and responds to the operation of swiping up from the bottom and pausing, and these multiple foreground visible applications are simultaneously exited individually; at this time, these multiple foreground visible applications correspond to the same task card 151.

[0067] In this embodiment, each task card can be used to display the display status of the application corresponding to that task card. Each task card may include various card information such as the application's layer, the application's name, and the application's icon. The application's layer can be drawn based on the application's window displayed on the screen. The application's layer may include the display content (or application display content) within the application's window.

[0068] Specifically, for foreground visible applications launched on a tablet in multitasking mode, since the size of the small window of the foreground visible application displayed on the tablet is smaller than the display area of ​​the screen, the multitasking card corresponding to this foreground visible application can include not only the content displayed in the application's small window but also a card background. Displaying the content of the application's small window on the card background can demonstrate the display status of the application's small window on the display area.

[0069] For example, such as Figure 2 As shown in (b), the size of the small window 121 of application A, which is visible in the foreground, is smaller than the size of the display area. For example, as... Figure 3 As shown in (b), the sizes of the small window 121 of the foreground visible application A, the small window 122 of the foreground visible application B, the small window 123 of the foreground visible application C, and the window 124 of the foreground visible application D are all smaller than the size of the display area.

[0070] Optionally, the background color of the card is usually semi-transparent. Figure 2 In (c) and (d), the semi-transparent color of the card background in multitasking card 141 is not shown. Figure 3 In (c) and (d), the semi-transparent color of the card background in the multitasking card 151 is not shown.

[0071] Optionally, the multitasking card of the foreground-visible application may also include a multitasking icon 111 displayed in multitasking scheduling mode. For example, as shown... Figure 2 As shown in (c), the task card 141 corresponding to application A includes: the display content of application A, the name of application A is "Gallery", the multitasking icon 111, and the card background.

[0072] Secondly, regarding background applications on tablets, before exiting the multitasking mode, the tablet displays one or more background applications in full screen. Therefore, the task cards corresponding to the background applications do not include card backgrounds. For example, as... Figure 4 As shown in (a), the task card 211 corresponding to a background application displayed on the tablet computer's end screen 210 does not include a card background. For example, as... Figure 4As shown in (b), the task cards 221 corresponding to the two background applications displayed on the tablet computer in the end screen 220 do not include card backgrounds.

[0073] In this embodiment, for foreground visible applications launched by a tablet computer in multitasking mode, each image frame in the `recents` animation includes a multitasking card corresponding to the foreground visible task. The multitasking card includes a card background, and this background varies at different stages of the `recents` animation. Specifically, the `recents` animation includes a follow animation, an end animation, and an end screen. In the follow animation and the end animation, the tablet computer uses a background layer as the card background, and this background layer changes as the foreground visible application layer in the multitasking card changes. That is, the background layer and the foreground visible application layer are simultaneously scaled and moved. In the end screen, the tablet computer uses a background view (or background view) as the card background. This background view is displayed in the end screen, and its size and position are fixed.

[0074] Optionally, the background layer and the background view can be semi-transparent. Figure 5 In (a) and (b), diagonal stripes are used to represent the semi-transparent color of the background layer and the semi-transparent color of the background view. The greater the density of the diagonal stripes, the darker the semi-transparent color. Diagonal stripes of the same density represent the same semi-transparent color.

[0075] The tablet begins a memory release and cleanup process as the recents animation nears its end. This process includes destroying the background layer. The tablet also redraws and makes the background view visible at the end of the recents animation, ensuring it appears in the final frame of the animation. Figure 5 As shown in (a), because the background layer is not destroyed when the background view is displayed, the tablet displays both the background layer and the background view in the multitasking card 310. The overlap of the background layer and the background view can cause the background color of the multitasking card to darken, especially the overlap of a semi-transparent background layer and the background view, which significantly darkens the background color of the multitasking card, for example, as shown in Figure [figure missing]. Figure 5As shown in (a), the background of the multitasking card changes from multitasking card 311 to multitasking card 312. Therefore, when the tablet displays a background layer in the multitasking card, and then displays both the background layer and background view in the multitasking card, the background color of the multitasking card darkens, visually causing a jump in the task card corresponding to the foreground application. Furthermore, when the tablet destroys the background layer and then displays both the background layer and background view in the multitasking card, and then displays only the background view in the multitasking card, the background color of the multitasking card lightens, also visually causing a jump in the multitasking card. For example, as... Figure 5 As shown in (a), the background of the card changes again when switching from multitasking card 312 to multitasking card 313. The two transitions between the multitasking cards cause a flickering visual effect in the recents animation, resulting in an unsmooth user experience.

[0076] It should be noted that, Figure 5 The multitasking cards 311, 312 and 313 shown in (a) are the same multitasking card displayed at different stages of the recents animation.

[0077] To address the aforementioned issues, this application provides a method for displaying multitasking animations. Considering that the overlapping of a background layer and a background view causes changes in the background color of the multitasking card, the electronic device can detect the drawing of the background view in real time and hide or destroy the background layer before the background view is drawn. This avoids simultaneously displaying the background layer and background view in the multitasking card. The multitasking card displays either the background layer or the background view, and since the background layer and background view have the same color, the background color of the multitasking card can remain unchanged, solving the problem of jumps in the multitasking card during recent animations. This avoids flickering in recent animations, ensuring smooth playback and providing a better visual experience for users. For example, as... Figure 5 As shown in (b), the backgrounds of multitasking cards 321, 322, and 323 are all the same.

[0078] It should be noted that, Figure 5 The multitasking cards 321, 322, and 323 shown in (b) are the same multitasking card displayed at different stages of the recents animation.

[0079] This application provides a method for displaying multi-task animation, which can be applied to electronic devices with multi-task scheduling mode and recents function, such as tablet computers, personal computers (PCs), laptops, mobile phones, in-vehicle devices, or wearable devices (e.g., smart bracelets). This application does not limit the specific type of electronic device.

[0080] Take a tablet computer as an example. Figure 6 A schematic diagram of the structure of the electronic device provided in this application is shown.

[0081] Reference Figure 6 As shown, the electronic device may include a processor 610, an external memory interface 620, an internal memory 621, a universal serial bus (USB) interface 630, a charging management module 640, a power management module 641, a battery 642, antenna 1, antenna 2, a mobile communication module 650, a wireless communication module 660, an audio module 670, a speaker 670A, a receiver 670B, a microphone 670C, a headphone jack 670D, a sensor module 680, buttons 690, a motor 691, an indicator 692, one or more displays 693, a subscriber identification module (SIM) card interface 694, and a camera 695, etc. The sensor module 680 may include pressure sensors, touch sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, ambient light sensors, bone conduction sensors, etc.

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

[0083] A controller can be the nerve center and command center of an electronic device. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

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

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

[0086] The external memory interface 620 can be used to connect to external non-volatile memory, thereby expanding the storage capacity of electronic devices. The external non-volatile memory communicates with the processor 610 through the external memory interface 620 to perform data storage functions. For example, music, video, and other files can be stored in the external non-volatile memory.

[0087] The internal memory 621 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). The RAM can be directly read and written by the processor 610 and can be used to store executable programs (e.g., machine instructions) of the operating system or other running programs, as well as user and application data. The NVM can also store executable programs and user and application data, and can be pre-loaded into the RAM for direct reading and writing by the processor 610. In this embodiment, the internal memory 621 may store image files or recorded video files captured by the electronic device in single-lens or multi-lens shooting modes.

[0088] A touch sensor, also known as a "touch device," can be located on the display screen 693. A touchscreen consisting of the touch sensor and the display screen 693 is also called a "touchscreen." The touch sensor detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 693. In other embodiments, the touch sensor may also be located on the surface of the electronic device, in a different position than the display screen 693.

[0089] In this embodiment, the touch sensor can detect user input such as swiping up from the bottom, swiping up from the bottom and pausing, and transmit the information of this operation to the processor 610 in real time. The processor 610 analyzes the function corresponding to the operation, such as hiding or destroying the background layer in advance, or displaying the recent animation.

[0090] A pressure sensor is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor may be located on the display screen 693. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may consist of at least two parallel plates made of conductive material. When a force is applied to the pressure sensor, the capacitance between the electrodes changes. The electronic device determines the pressure intensity based on the change in capacitance. When a touch operation is applied to the display screen 693, the electronic device detects the intensity of the touch operation based on the pressure sensor. The electronic device can also calculate the touch location based on the detection signal from the pressure sensor.

[0091] Electronic devices implement display functions through a GPU, a display screen 693, and an application processor. The GPU is a microprocessor that shares images, connecting the display screen 693 and the application processor. The GPU performs mathematical and geometric calculations for graphics rendering. The processor 100 may include one or more GPUs, which execute program instructions to generate or modify display information.

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

[0093] Of course, this is understandable. Figure 6 The illustration shown is merely an example when the electronic device is in the form of a tablet computer. If the electronic device is in the form of a mobile phone, PC, or wearable device, the structure of the electronic device may include more... Figure 6 The fewer structures shown can also include more than Figure 6 The structures shown are not limited here.

[0094] It is understandable that the implementation of electronic device functions requires not only hardware support but also the cooperation of software architecture. In some examples, refer to... Figure 7 As shown, the operating system used by the electronic device is Android. TM Taking a system as an example, the software architecture of the electronic device provided in this application may include: an application layer, an application framework layer, and a kernel layer. It should be noted that the embodiments in this application use Android... TM To illustrate, let's take an example from other operating systems (such as HarmonyOS). TM System, iOS TM Any system (or similar system) can achieve the solution of this application as long as the functions implemented by each functional module are similar to those in the embodiments of this application.

[0095] The application layer can include a series of application packages. For example... Figure 5 As shown, the application package may include floating windows, video, gallery, email, music, messaging, map, instant messaging applications, and other applications. Of course, the application layer may also include other application packages, such as Bluetooth, calendar, shopping applications, chat applications, etc., and this application does not limit this.

[0096] In this embodiment, the application layer may also include a desktop launcher. The launcher has the following functions: (1) Determine the touch operation area: The launcher can identify the touch position of the user's touch operation, and thus respond to the corresponding application launch or other interactive actions according to the touch operation and touch position; (2) Launch animation: The launcher is responsible for managing and executing the animation effects on the desktop, such as the bouncing of icons, the transition effect of application launch, etc.; (3) Update the application layer: The launcher can update the application layer according to the user's swiping operation; for example, when the user swipes to different desktop pages or performs folder operations, the launcher will dynamically update the layout and display mode of the application icons on the display screen so that the user can easily access and organize their applications; (4) Personalization settings: In addition to basic operation functions, the launcher also allows users to make personalization settings, such as adjusting the icon size, adding widgets, etc.

[0097] The application framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The application framework layer includes predefined functions such as system servers, system user interfaces (System UI), surface managers, surface flingers, activity managers, window managers, view systems, resource managers, notification managers, and camera services, etc. This application embodiment does not impose any limitations on these.

[0098] Among them, system servers are part of Android. TM One of the core services of the system is the system server, which is responsible for managing and running various system services. These services include, but are not limited to, the Activity Manager and the Window Manager. After the system server starts, it initializes and manages these critical system services to ensure the normal operation of the entire system.

[0099] System UI is Android TMThe system's user interface components include the status bar, notification bar, lock screen, and navigation bar. It is responsible for displaying user interface elements and providing ways to interact with the user, such as receiving user input and displaying system status information.

[0100] Surface Manager is an Android feature. TM A crucial component of the system, it manages and allocates the display of all surfaces on the screen, including application windows, system UI, etc. Closely related to the surface flinger, it is responsible for allocating buffers for each surface, tracking the position and hierarchy of each surface, and managing the lifecycle of the surfaces.

[0101] Surface flinger is an Android app. TM A system-level service within the system, responsible for displaying all 2D and 3D graphics elements. It manages all surfaces on the display screen. The surface flinger is responsible for compositing all surfaces and outputting the final image to the display screen.

[0102] The kernel layer is the layer between hardware and software. It interacts directly with the hardware and provides a variety of basic system services and functions. The kernel layer shields upper-layer software from hardware details, ensuring system stability and compatibility. The kernel layer contains drivers for various hardware devices, such as display drivers, camera drivers, audio drivers, and sensor drivers, allowing upper-layer software to operate without needing to know the specific implementation details of the hardware.

[0103] Based on the above hardware and software architecture, the following uses a tablet computer as an example to introduce the method for displaying multi-task animation provided in the embodiments of this application.

[0104] Reference Figure 8 The diagram shown is a flowchart illustrating a method for displaying multi-tasking animation according to an embodiment of this application. This display method can be applied to tablet computers, for example... Figure 7 The tablet computer shown may include a launcher and a surface flinger. The tablet computer can execute this display method through the launcher and surface flinger, such as... Figure 8 As shown, the specific process may include S801-S814.

[0105] S801, the launcher receives and responds to user input press operations, and obtains the touch position of the press operation.

[0106] When a tablet displays one or more foreground applications in small windows, it can receive user input (i.e., a down action) and transmit this down action to the launcher. The launcher can obtain the coordinates of the down action within the tablet's display area, which can be used to represent the touch position of the down action. The tablet's display area can be divided into multiple different areas (e.g., a top area, a bottom area, etc.). Furthermore, the launcher can respond accordingly based on any of the areas to which the coordinates belong, i.e., perform the corresponding application launch or other interactive action. For example, if the launcher determines that the coordinates belong to the bottom area of ​​the display area, it executes step S802.

[0107] In this embodiment, the down operation can be one of multiple touch operations input by the user in succession. Furthermore, after receiving the down operation, the launcher can continue to detect and respond to other touch operations following the down operation.

[0108] For example, the down operation can be one of the user's input operations of swiping up from the bottom and pausing. When the user inputs the swipe-up-from-the-bottom-and-pause operation into the tablet, the launcher can continuously receive the user's input down operation, swipe operation (i.e., move operation), and raise operation (i.e., up operation) in sequence. That is to say, after receiving the down operation, the launcher can also receive the move operation and the up operation.

[0109] For example, such as Figure 2 As shown in (b), when the tablet displays a small window 121 of a foreground application A in multitasking mode, it can receive user input by swiping up from the bottom and pausing. For example, as... Figure 3 As shown in (b), when the tablet displays small windows of multiple foreground visible applications in multitasking mode, it can receive user input by swiping up from the bottom and pausing.

[0110] S802, when the launcher is located in the bottom area of ​​the display area, determines the animation elements; the animation elements include tasks visible in the foreground.

[0111] When the launcher determines that the down operation is located in the bottom area, it indicates that the down operation may be a down operation within a swipe-up-and-pause action from the bottom. Since the swipe-up-and-pause action from the bottom is used to trigger the display of the recents animation, the launcher can begin the preparation process for displaying the recents animation when it determines that the down operation is located in the bottom area. This preparation process may include determining the animation elements. The animation elements may include all foreground visible tasks.

[0112] In this embodiment, the bottom area may refer to the interactive area located at the bottom of the display area of ​​the tablet computer. Optionally, this bottom area may be referred to as the bottom hot zone.

[0113] In this embodiment, the tablet computer can traverse all running tasks on the tablet and determine whether each task is visible when it is encountered. If any task is visible, it means that the task is a foreground visible task, and it can be determined that the task belongs to the animation element. If any task is not visible, no processing is required for that task.

[0114] In this context, a task can be understood as a complete operational flow of an application during its execution. An application can contain multiple tasks; for example, a tablet can run multiple tasks in a note-taking application to manage different notes. A foreground visible application can include foreground visible tasks. When each foreground visible task belongs exclusively to one application, the foreground visible task is equivalent to the foreground visible application.

[0115] For example, such as Figure 2 As shown in (b) above, the tablet displays a small window 121 of a foreground application A, so the motion effect element can include the foreground application A. For example, as... Figure 3 As shown in (b), the tablet displays multiple small windows of foreground visible applications (including small window 121 of foreground visible application A, small window 122 of foreground visible application B, small window 123 of foreground visible application C, and small window 124 of foreground visible application D). The animation elements can include foreground visible application A, foreground visible application B, foreground visible application C, and foreground visible application D.

[0116] In some embodiments, the tablet computer also includes a system-level user interface (System UI) and a system server. S802 may include the following steps: when the launcher is located in the bottom area of ​​the display area, it creates a multi-task animation callback (or recents animation callback) and starts an animation task (or recents task); after the launcher starts the animation task, the System UI sends a first instruction to the system server to start the transition; the system server receives and responds to the first instruction to start the transition; the system server iterates through all tasks running on the tablet computer to determine the animation elements.

[0117] The system server can also store instances of each foreground visible task in an instance collection. Each instance of a foreground visible task can include information about the small window of that foreground visible task, such as the small window's identity (ID), the small window's region information (e.g., the region information can include the small window's position information on the display area), the small window's size (e.g., including the small window's width and height), and the small window's hierarchy.

[0118] For example, the multi-task animation callback created by the launcher can include methods involved in the entire processing of the recent animation, specifically including: a method to start the recent animation, a method to cancel the recent animation, and a method to end the recent animation. For example, the launcher can create the recent animation callback using `new RecentsAnimationCallback()`. `RecentsAnimationCallback()` can include: the `onAnimationStart()` method to start the recent animation, the `onAnimationCancel()` method to cancel the recent animation, and the `onAnimationEnd()` method to end the recent animation. The launcher can start the recent task by calling the `startRecentsActivity()` method.

[0119] In some embodiments, on Android TMIn the system, a "transition" typically refers to the smooth transition of the user interface (UI) from one state to another. For example, the recents animation between the desktop interface 100 and the multitasking management interface 140 is a transition. The system server initiates the recents animation by starting a transition. For instance, the system server can start a transition by calling the startTransition() method.

[0120] S803, the launcher triggers the creation of the motion target corresponding to each foreground visible task in the motion effect element, and triggers the creation of the background layer; wherein, the motion target includes the layer of each foreground visible task, and the size of the layer of each foreground visible task is smaller than the size of the display area; the size of the background layer is equal to the size of the display area.

[0121] The tablet can draw a layer for each foreground application based on its small window. The tablet can also create a blank background layer with a size equal to the display area. The tablet displays this background layer and the layers of all foreground applications simultaneously in the multitasking card, showing the display status of the small windows of the foreground applications within the display area.

[0122] In the recents animation, the multitasking cards undergo scaling and movement updates, and the background layer and all foreground visible task layers in the multitasking cards are simultaneously scaled and moved. After the tablet performs scaling and movement updates on the background layer and foreground visible task layers, the updated background layer is smaller than the display area, and the updated foreground visible layers are also reduced in size.

[0123] In some embodiments, S803 may include the following steps: the system server starts a multi-task remote animation and sends a second instruction carrying animation elements to the System UI; the second instruction may include animation elements; the System UI receives and responds to the second instruction, constructing an animation target (or animation target) corresponding to each foreground visible task in the animation element; during the construction of the animation target corresponding to each foreground visible task, the System UI may call the surface flinger to create a layer for each foreground visible task in the animation element; the System UI triggers an animation start callback, sending the animation targets corresponding to all foreground visible tasks to the launcher.

[0124] The animation target for each foreground visible task can include: an instance of that foreground visible task stored in the instance collection, and a layer for that foreground visible task. Surface Flinger can create a layer for each foreground visible task based on an instance of that foreground visible task (including information about the window of that foreground visible task).

[0125] In some embodiments, the surface flinger can draw the layer of each foreground visible task based on the window of that foreground visible task. The layer of the foreground visible task changes synchronously with the state of the window of that foreground visible task. For example, when the window of the foreground visible task is moved, minimized, enlarged, or closed, the surface flinger updates the layer of the foreground visible task accordingly. The size of the layer of the foreground visible task can be equal to the size of the window of that foreground visible task.

[0126] S804, the launcher receives and responds to the user's input swipe action, updates the background layer and the layer of each foreground visible task in the animation element, and sends the updated background layer and the updated foreground visible task layer to the surface flinger.

[0127] The launcher can receive multiple move operations in succession after a down operation. For each swipe operation, the launcher can execute S804.

[0128] In some embodiments, S804 may include the following steps: the launcher updates the animation progress according to the sliding distance and sliding speed of each move operation in response to each move operation; the launcher updates the properties of the background layer and the properties of each animation target in all animation targets according to the updated animation progress; the launcher sends a third instruction to the surfaceflinger, the third instruction being used to trigger the update of the background layer and the update of the foreground visible task layer corresponding to each animation target, the third instruction including the properties of the background layer and the properties of each animation target; the surfaceflinger updates the foreground visible task layer corresponding to each animation target based on the properties of each animation target in response to the third instruction, and also updates the background layer based on the properties of the background layer.

[0129] The initial value of the animation progress can be 0. The launcher responds to multiple move operations and the animation progress keeps increasing, for example, from 10% to 20%, and then from 20% to 30%, and so on.

[0130] Optionally, the background layer's properties may include its displacement, rounded corners, scaling, cropping, and opacity, etc. Each motion target's properties may include its displacement, rounded corners, scaling, cropping, and opacity, etc.

[0131] S805 and Surface Flinger generate an image frame in the follow animation based on the updated background layer and the updated foreground visible task layer; wherein each image frame in the follow animation includes a multitasking card, and the multitasking card displays the background layer and the foreground visible task layer.

[0132] After Surface Flinger generates each image frame in the follow animation, the tablet computer can control the display to show that image frame.

[0133] In this embodiment, the recents animation can be divided into multiple stages, specifically including a follow-up animation, an ending animation upon entering the multitasking management interface, and an ending screen. Regardless of the stage of the recents animation, each image frame in the recents animation includes task cards corresponding to all currently running tasks. The task cards corresponding to all currently running tasks can include: a multitasking card that corresponds to all foreground visible tasks.

[0134] In this embodiment, each task card (e.g., a multitasking card) may include: the display content of the application corresponding to the task card in the display area (i.e., the display content of the application). Each task card may also include at least one of the following: the name of the application corresponding to the task card, the icon of the application corresponding to the task card, and other card information. For example, other card information in a multitasking card may include: a background layer and a multitasking icon for representing the multitasking scheduling mode.

[0135] Optionally, each task card (e.g., a multi-task card) may include a variety of card information, and the card information displayed for each task card may be different at different stages of the recall animation.

[0136] For example, see Figure 9 Image (b) is a schematic diagram illustrating the display content of multiple stages in a recents animation provided in an embodiment of this application. In the follow-up animation and the ending animation, the tablet displays a background layer and the layer of each foreground visible application (including the display content of each foreground visible application) in the multitasking card, but does not display the name or icon of each foreground visible application. In the ending screen, the tablet displays the multitasking icon and the name of each foreground visible application in the multitasking card.

[0137] For example, such as Figure 2 As shown in (c), the tablet computer only displays the content of the foreground application A in the multitasking card 141 of the follow animation. Figure 2 As shown in (d) in the end screen, the tablet computer displays the content of the foreground visible application A, the name of the foreground visible application A (i.e., the gallery), and the multitasking icon 111 in the multitasking card 141.

[0138] For example, such as Figure 3 As shown in (c), the tablet displays only the content of multiple foreground visible applications in the multitasking card 151 of the follow animation. Figure 3 As shown in (d) in the end screen, the tablet displays the content of multiple foreground visible applications, the names of multiple foreground visible applications (including Gallery, Notes, Messages and Videos), and a multitasking icon 111 in the multitasking card 151.

[0139] Optionally, the multitasking card can utilize a layer of foreground visible applications to display the content of the foreground visible applications. This layer is drawn based on the small window of the foreground visible application displayed on the screen, and can include the content displayed within that small window (i.e., the content of the foreground visible application).

[0140] In some embodiments, when the applications running on the tablet include background applications, each image frame in the recents animation may include a multitasking card corresponding to the foreground application and a task card corresponding to the background application. The tablet can display the task view of the background application in the task card corresponding to the background application. The task view of the background application may include a screenshot of the background application. The task view of the background application may also include at least one of the following: the name of the background application and the icon of the background application, etc. The screenshot of the background application may include the content displayed in the window of the background application shown on the screen (or the display content of the background application). The tablet can display the display content of the background application using the screenshot in the task card corresponding to the background application.

[0141] Optionally, the background application's taskview can include various card information (e.g., a screenshot of the background application, the name of the background application, and the icon of the background application), and the card information displayed on the background application's task card can be different at different stages of the recall animation. That is, the card information included in the background application's taskview in the background application's task card is different at different stages of the recall animation.

[0142] For example, such as Figure 10 As shown, in the follow-up and end animations, the tablet displays a screenshot of the background application in the background application's task card, but does not display the application's name or icon. In the end screen, the tablet displays a screenshot, the application's name, and its icon in the background application's task card.

[0143] A screenshot of any application (e.g., a screenshot of a background application) can be obtained by taking a screenshot of the application's window displayed on the screen. A screenshot of any application is a static image. A screenshot of any application can be an image of the application's window displayed on the tablet at any given moment; for example, a screenshot of a background application can be obtained by taking a screenshot of the background application's window displayed on the screen at a moment before the tablet exits the background application.

[0144] Furthermore, if the task the tablet is running also includes background tasks, the launcher responds to each swipe by updating the background layer and the layers of all foreground visible tasks, as well as the taskview of the background tasks; then, the surface flinger can generate an image frame in the swipe animation based on the updated background layer, the updated layers of all foreground visible tasks, and the updated taskview of the background tasks.

[0145] S806, the launcher receives and responds to the user's hand-raising operation, and determines the purpose of the hand-raising operation's animation.

[0146] After receiving a down action applied to the bottom area and multiple move actions, the launcher can receive an up action input by the user. In response to the up action, the launcher can first determine the purpose of the up action's animation, and then perform the corresponding operation based on that purpose.

[0147] In some embodiments, if a pause in the touch operation is detected before the up operation, it is determined that the purpose of the up operation is to enter the multitasking management interface, and S807 is executed. If a pause in the touch operation is detected before the up operation, it is determined that the purpose of the up operation is not to enter the multitasking management interface. The purpose of the up operation in a user-inputted swipe-up-from-the-bottom and pause operation is to enter the multitasking management interface.

[0148] For example, such as Figure 11As shown, after S806, the tablet can execute S1101. S1101 includes determining whether the purpose of the up operation's animation is to enter the multitasking management interface. If the purpose of the up operation's animation is to enter the multitasking management interface, then S1102 is executed, i.e., the ending animation of entering the multitasking management interface is displayed. S1102 can include S807-S808. If the purpose of the up operation's animation is not to enter the multitasking management interface, then S1103 is executed. S1103 can include: based on the sliding distance, sliding speed, and sliding direction of the move operation before the up operation, displaying the desktop interface, returning to the currently displayed application, or launching a new application.

[0149] When the purpose of the animation is to enter the multitasking management interface, the S807 launcher updates the background layer and the layer of each foreground visible task in the animation element, and sends the updated background layer and the updated foreground visible task layer to the surface flinger.

[0150] It should be noted that for details regarding the launcher's response to the up operation to update the background layer and the layers of each foreground visible task, please refer to the above description of the launcher's response to the move operation to update the background layer and the layers of each foreground visible task. Unlike the launcher, which updates the animation progress based on the sliding distance and speed of the move operation, the launcher can update the animation progress to 100% in response to the up operation.

[0151] S808 and Surface Flinger generate an ending animation for entering the multitasking management interface based on the updated background layer and the updated foreground visible task layer; each frame in the ending animation includes a multitasking card, which displays the background layer and the foreground visible task layer.

[0152] The last image frame in the ending animation could be a multitasking management interface, for example, Figure 2 The multi-task management interface 140 shown in (d) and Figure 3 The multitasking management interface 150 is shown in (d) in the figure.

[0153] In some embodiments, the duration of the ending animation is shorter than the duration of the follow animation. For example, the duration of the ending animation may be equal to 500 milliseconds (ms).

[0154] It should be noted that for details on how the launcher generates each image frame in the ending animation in response to the up operation, please refer to the above-mentioned specific introduction on how the launcher generates one image frame in the follow animation in response to the move operation.

[0155] S809, when the launcher ends the animation, it triggers the rendering thread in the launcher to draw all the taskviews corresponding to the foreground visible tasks and make them visible.

[0156] Optionally, the end of the animation may refer to the completion of the drawing of the last image frame in the animation (i.e., the multitasking management interface), or it may refer to the sending of the last image frame in the animation to the display screen.

[0157] In this embodiment, the taskview corresponding to all foreground visible tasks may include a background view and a screenshot of each foreground visible task. It may also include at least one subview: a multitasking icon and each foreground visible task. The screenshot of the background application may include the content displayed in the window of the background application shown on the screen (or the display content of the background application). The tablet computer can display the display content of the background application using the screenshot in the task card corresponding to the background application. The background view and the screenshot of each foreground visible task are also subviews of the taskview.

[0158] Details regarding the screenshots of each foreground visible task can be found in the specific description of screenshots for an application described above. Optionally, the screenshot of each foreground visible task can be a snapshot taken of the small window of that foreground visible task displayed on the screen at a moment before the recents animation is displayed. For example, as... Figure 2 As shown in (b), a screenshot of the foreground visible application A can be a screenshot of the small window 121 of the foreground visible application A displayed on the screen. For example, as... Figure 3 As shown in (b), a screenshot of the foreground visible application B can be a screenshot of the small window 122 of the foreground visible application B displayed on the screen.

[0159] For example, the launcher can trigger the drawing of all taskviews corresponding to foreground visible tasks through the Onframedraw() method in the onAnimationEnd() method, and make all taskviews corresponding to foreground visible tasks visible through the setVisibility() method in the onAnimationEnd() method.

[0160] In some embodiments, the tablet computer can determine and update the size of the subviews in the taskviews corresponding to all foreground visible tasks based on the size of the layers in the multitasking management interface. For example, the size of the background view in the taskviews corresponding to all foreground visible tasks can be equal to the size of the background view in the multitasking management interface, and the size of the screenshot of each foreground visible task in the taskviews corresponding to all foreground visible tasks can be equal to the size of the layer of that foreground visible task in the multitasking management interface.

[0161] When S810 and launcher determine that they have entered multi-task scheduling mode, they register taskview drawing callbacks with the rendering thread. The taskview drawing callbacks are used to notify launcher when the drawing of the taskviews corresponding to all foreground visible tasks is completed.

[0162] When the launcher determines that the animation has ended, it triggers the drawing of all taskviews corresponding to the foreground visible tasks and makes them visible. At the same time, if it determines that it has entered multi-task scheduling mode, it registers taskview drawing callbacks with the rendering thread. In other words, the launcher can execute S809 and S810 simultaneously.

[0163] For example, such as Figure 11 As shown, when the launcher finishes the animation, it executes S1104 and S1105. S1104 includes triggering the drawing of all taskviews corresponding to the foreground visible tasks and making them visible. S1105 includes determining whether the tablet has entered multi-tasking mode. If it is determined that it has entered multi-tasking mode, it executes S1106, which includes monitoring the drawing of the task view and hiding or destroying the background layer in advance when the task view drawing is completed; then it displays the ending screen. Optionally, S1106 may include S810-S812. If it is determined that it has exited multi-tasking mode, it may execute S1107, which includes directly displaying the ending screen and performing the memory release and cleanup process for the recent animation.

[0164] For example, the launcher can register the taskview drawing callback with the rendering thread through the RegisterRtframeCallback() method in the onAnimationEnd() method.

[0165] S811. When all taskviews corresponding to the foreground visible tasks have been drawn, the launcher sends all taskviews corresponding to the foreground visible tasks, as well as the hiding method for hiding the background layer, to the surfaceflinger.

[0166] When the animation ends, the rendering thread executes the taskview drawing callback to notify the launcher that the drawing of all taskviews corresponding to the foreground visible tasks is complete. When the launcher receives the notification that the drawing of all taskviews corresponding to the foreground visible tasks is complete, it sends all taskviews corresponding to the foreground visible tasks, as well as the hiding method used to hide the background layer, to the surface flinger.

[0167] For example, the launcher sends the `mergeWithNextTransaction()` method to the surface flinger. The `mergeWithNextTransaction()` method includes the frame number of the most recently drawn taskview and a `hide()` method for hiding the background layer. Before all taskviews corresponding to foreground visible tasks are sent to the surface flinger, the launcher's rendering thread can continuously draw all taskviews corresponding to foreground visible tasks. The rendering thread executes the taskview drawing callback after drawing all taskviews corresponding to foreground visible tasks for the first time. Further, when sending all taskviews corresponding to foreground visible tasks to the surface flinger, the launcher can send the frame number of the most recently drawn taskview to the surface flinger, so that the surface flinger generates the final screen based on the most recently drawn taskview. The most recently drawn taskview is the taskview corresponding to all foreground visible tasks.

[0168] S812 and Surface Flinger generate an ending screen based on the taskviews corresponding to all visible tasks in the foreground and the hide function used to hide the background layer. The multitasking card in the ending screen displays the taskviews corresponding to all visible tasks in the foreground, and the background layer in the multitasking card in the ending screen is hidden. The taskviews corresponding to all visible tasks in the foreground include the background view.

[0169] For example, Surface Flinger can generate an end screen based on the taskviews, background layers, and layers of all foreground visible tasks, and hide the background layer in the end screen. The tablet computer can then control the display to show this end screen and hide the background layer of the multitasking cards within it.

[0170] For example, see Figure 9 (a) is a schematic diagram of the display content of multiple stages in a recents animation provided by the prior art. The prior art displays the background layer and all task views (including background views) corresponding to the foreground visible applications in the end screen at the same time. Compared with the multitasking card in the end animation which only displays the background layer, the multitasking card in the end screen displays both the background layer and the background view, causing the background of the multitasking card to change. Then, when the background layer is destroyed during the memory cleanup and release process, the multitasking card in the end screen only displays the background view again, causing the background of the multitasking card to change again.

[0171] See Figure 9 (b) is a schematic diagram illustrating the display content of multiple stages in a recents animation provided in an embodiment of this application. In this embodiment, the tablet computer begins to hide the background layer when the background view is drawn, ensuring that the multitasking card in the ending screen only displays the background view. The fact that the multitasking card in the ending animation only displays the background layer and the multitasking card in the ending screen only displays the background view ensures that the background of the multitasking card remains unchanged.

[0172] It should be noted that, Figure 9 The lengths of each stage in the recents animation shown in (a) and (b) are not related to the actual duration of each stage in the recents animation in actual application, and cannot reflect the actual duration of each stage in the recents animation in actual application.

[0173] When the S813 launcher ends the animation, it triggers a memory release and cleanup process; the memory release and cleanup process includes destroying the background layer.

[0174] When the launcher finishes the ending animation in the `recents` animation, it can trigger a memory release and cleanup process for the `recents` animation to ensure that related resources are released after the `recents` animation ends. This memory release and cleanup process can include: resource reclamation and memory release, destruction of layers or views, and triggering a UI redraw or refresh. Resource reclamation and memory release can include releasing the memory and resources allocated during the display of the `recents` animation, specifically including temporary memory and GPU resources used by the `recents` animation. Destroying layers or views may include, depending on the specific implementation, destroying or reusing layer or view objects created during the display of the `recents` animation. Triggering a UI redraw or refresh ensures that the final state is correctly displayed after the `recents` animation ends.

[0175] For example, the memory release and cleanup process may include: the launcher calling the surfacecontrolrelease() method to destroy the background layer, and the System UI destroying the layers of all foreground visible tasks.

[0176] In this embodiment of the application, the launcher generates and displays the ending screen, and the recents animation ends.

[0177] Optionally, Figure 11 S1106 in the formula may exclude S811-S812, but include S814-S815.

[0178] For example, the launcher can be implemented using the following pseudocode. Figure 11 S1101-S1107 in the middle:

[0179] If (entering the multitasking management interface && multitasking scheduling mode is enabled)

[0180] {

[0181] Monitor the drawing of the task view, and hide or destroy the background layer when drawing is complete;

[0182] The end screen will be displayed;

[0183] }else{

[0184] Display the end screen and execute the memory release and cleanup process for the recents animation;

[0185] }

[0186] "Entering the multitasking management interface" could mean that the purpose of the up operation animation is to enter the multitasking management interface. "Entering the multitasking management interface" could also mean that the tablet computer enters multitasking management mode.

[0187] Understandably, by monitoring the drawing of all visible task views in real time (or monitoring task view drawing), tablets can precisely determine when a task view is completed. This allows them to hide the background layer at the moment the task view is finished drawing, avoiding the background color changes in multitasking cards caused by simultaneously displaying the background layer and the background view within the task view. This ensures the background color of multitasking cards remains constant, resolving the issue of jumps in multitasking cards during the recent animation. It also solves the flickering problem in the recent animation, ensuring smooth playback and providing a better visual experience for users.

[0188] In some embodiments, the tablet may not hide the background layer but destroy it beforehand, once the taskviews corresponding to all foreground visible tasks have finished drawing. For example... Figure 12 As shown, the multi-task animation display method provided in this application embodiment may exclude S811-S813 after S810, and include S814-S816 instead.

[0189] S814. When all taskviews corresponding to the foreground visible tasks have been drawn, the launcher sends all taskviews corresponding to the foreground visible tasks to the surfaceflinger and destroys the background layer.

[0190] For example, see Figure 9 (b) is a schematic diagram illustrating the display content of multiple stages in a recents animation provided in an embodiment of this application. The tablet computer destroys the background layer in advance when the background view is drawn, without waiting for memory release and cleanup to destroy the background layer. This ensures that the multitasking card in the ending screen only displays the background view. Since the multitasking card in the ending animation only displays the background layer, and the multitasking card in the ending screen only displays the background view, the background of the multitasking card remains unchanged.

[0191] For example, the launcher can destroy the background layer using the surfaceControlRelease() method.

[0192] The S815 and Surface Flinger generate an ending screen based on the taskviews corresponding to all visible tasks in the foreground. The multitasking cards in the ending screen display the taskviews corresponding to all visible tasks in the foreground, and the multitasking cards in the ending screen do not include the background layer. The taskviews corresponding to all visible tasks in the foreground include the background view.

[0193] When the S816 launcher ends the animation, it triggers a memory release and cleanup process, which does not include destroying the background layer.

[0194] It should be noted that the steps executed by the launcher described above can all be implemented by the launcher calling the main process within the launcher.

[0195] Understandably, by monitoring the drawing of all visible task views in real time (or listening to task view drawing), tablets can precisely determine when a task view's drawing is complete. This allows them to destroy the background layer at the moment the task view finishes drawing, avoiding the background color changes in multitasking cards caused by simultaneously displaying the background layer and the background view within the task view. This ensures the background color of multitasking cards remains constant, resolving the issue of jumps in multitasking cards during the recent animation. It also solves the flickering problem in the recent animation, ensuring smooth playback and providing a better visual experience for users.

[0196] Reference Figure 13 The diagram shown is a flowchart illustrating a method for displaying multi-task animation according to an embodiment of this application. Figure 13 As shown, the display method may also include the following S1301-S1304.

[0197] S1301, The tablet computer displays a first interface; the first interface includes at least one first-type icon within a preset area and at least one second-type icon outside the preset area, the at least one first-type icon including a preset icon.

[0198] The preset icon can be used to control whether the tablet enters or exits multitasking mode. For example, the preset icon could be... Figure 1 The multitasking icon 111 is shown in (a) and (b) in the image.

[0199] It should be noted that the details of the preset icons can be found in the above description of the multitasking icons, and will not be repeated here in this embodiment.

[0200] For example, the first interface can be Figure 1 The desktop interface 100 shown in (a) is shown in the figure. The preset area in the first interface can be the Dock area 110 in the desktop interface 100. The icons of the applications in the Dock area 110 belong to the first type of icons, and the icons of the applications outside the Dock area 110 belong to the second type of icons.

[0201] S1302, the tablet computer displays a second interface in response to clicking a preset icon in the first interface; the second interface includes a preset area but does not include at least one second type of icon.

[0202] When a tablet responds to a click on a preset icon, it enters a multitasking mode (or activates multitasking mode), hides at least one secondary icon outside the preset area, and modifies the appearance of the preset icon. After hiding at least one secondary icon outside the preset area and modifying its appearance, the tablet displays a second interface. In other words, the tablet enters the second interface displayed by the multitasking mode and exits the first interface displayed by exiting (or disabling) multitasking mode.

[0203] The preset icon is displayed in a first form on the first interface and in a second form on the second interface. The first and second forms differ, for example, in color, line thickness, etc.

[0204] For example, the second interface can be Figure 1 The desktop interface 100 shown in (b) is shown in the figure. Figure 1 The desktop interface 100 shown in (b) only includes the Dock area 110 and does not include icons of applications outside the Dock area 110.

[0205] S1303, in the second interface, the tablet computer, in response to a first operation on a first icon in a preset area, displays a first window of a first application, the size of which is smaller than the size of the display area.

[0206] When a tablet enters multitasking mode and displays the second interface, it can receive the first operation that triggers the first application, displaying the first window of that application. Since tablets typically use small windows to display application windows in multitasking mode to allow multiple application windows to be displayed simultaneously, the size of the first window can be smaller than the display area. For example, as shown... Figure 2 As shown in (b), the first window of the first application can be a small window 121 of the foreground application A.

[0207] Optionally, the first action can be a click action.

[0208] S1304, the tablet computer responds to a second operation of swiping up from the bottom and pausing, and displays a multitasking animation; each frame of the multitasking animation includes a window background and the display content of a first window; the display content of the first window is displayed on top of the window background; the size of the window background is equal to the size of the display area; during the display of the multitasking animation, the size of the window background in the multitasking animation decreases, while the content of the window background remains unchanged.

[0209] When the tablet computer displays one or more application windows (i.e., small windows of foreground applications) in multitasking mode, it can receive a second user input: swiping up from the bottom and pausing. In response to this second input, a multitasking animation is displayed to show a transition from the current display interface to the multitasking management interface. The window background can refer to the card background of the multitasking card in the above embodiment.

[0210] For example, S1304 may include the above-described S801-S813.

[0211] For example, S1304 may include S801-S810 and S814-S816 as described above.

[0212] It is understood that, in order to achieve the aforementioned functions, the electronic device includes corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0213] This application embodiment can divide the above-described electronic device into functional modules based on the method example described above. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this embodiment is illustrative and only represents one logical functional division; in actual implementation, there may be other division methods.

[0214] This application also provides an electronic device, which includes: a memory and one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the multi-tasking animation display method provided in the foregoing embodiments.

[0215] This application also provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the multitasking animation display method provided in the foregoing embodiments.

[0216] This application also provides a computer program product containing executable instructions that, when run on an electronic device, cause the electronic device to execute the multitasking animation display method provided in the foregoing embodiments.

[0217] This application also provides a chip system, such as... Figure 14 As shown, the chip system 1400 includes at least one processor 1401 and at least one interface circuit 1402. The processor 1401 and the interface circuit 1402 are interconnected via lines. For example, the interface circuit 1402 can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit 1402 can be used to send signals to other devices (e.g., the processor 1401).

[0218] For example, interface circuit 1402 can read instructions stored in memory and send those instructions to processor 1401. When the instructions are executed by processor 1401, the chip system can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application embodiment does not specifically limit this.

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

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

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

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

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

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

Claims

1. A method for displaying multi-task animation, characterized in that, The method includes: Display a first interface; the first interface includes at least one first type of icon within a preset area and at least one second type of icon outside the preset area, the at least one first type of icon including a preset icon; In the first interface, in response to clicking the preset icon, a second interface is displayed; the second interface includes the preset area but does not include the at least one second-type icon. In the second interface, in response to a first operation on a first icon in the preset area, a first window of the first application is displayed, the size of the first window being smaller than the size of the display area; In response to a second operation of swiping up from the bottom and pausing, a multitasking animation is displayed; each frame of the multitasking animation includes a window background and the display content of the first window; the display content of the first window is displayed on top of the window background; the size of the window background is equal to the size of the display area; during the display of the multitasking animation, the size of the window background in the multitasking animation decreases while the content of the window background remains unchanged.

2. The method according to claim 1, characterized in that, During the display of the multitasking animation, the window background and the display content of the first window change synchronously; wherein, the synchronous change of the window background and the display content of the first window includes: the size of the window background and the size of the display content of the first window are scaled synchronously, and the position of the window background and the position of the display content of the first window are moved synchronously.

3. The method according to claim 1 or 2, characterized in that, The multi-task animation includes a follow-up animation, an end animation, and an end screen; the second operation includes: a press operation, a slide operation, and a pause followed by a release operation; The second action, responding to a swipe up from the bottom and pause, displays a multitasking animation, including: In response to the press operation, a blank background layer and a layer for the first application are created; the size of the background layer is equal to the size of the display area; the layer for the first application includes the display content of the first window; In response to the swipe operation, the background layer and the layer of the first application are updated, and each image frame in the follow animation is generated based on the updated background layer and the updated layer of the first application; the window background in each image frame of the follow animation displays the background layer; In response to the paused hand-raising operation, the background layer and the first application layer continue to be updated, and each image frame in the ending animation is generated based on the updated background layer and the updated first application layer; the window background in each image frame of the ending animation displays the background layer; The ending screen is generated based on the updated layers of the first application; the background layer is not displayed in the window background of the ending screen.

4. The method according to claim 3, characterized in that, Generating the final screen based on the updated layer of the first application includes: Upon completion of the ending animation, the drawing of the background view is triggered, and the drawing process of the background view is monitored; the size of the background view is equal to the size of the background layer in the last image frame of the ending animation. Once the background view is drawn, either the background layer is hidden or the background layer is destroyed. The ending screen is generated based on the background view and the updated first application layer; the window background in the ending screen displays the background view, but does not display the background layer.

5. The method according to claim 4, characterized in that, Both the background layer and the background view are semi-transparent.

6. The method according to claim 1 or 2, characterized in that, Prior to displaying the multitasking animation in response to the second action of swiping up from the bottom and pausing, the method further includes: In the second interface, in response to a third operation on the second icon in the preset area, a second window of the second application is displayed, the size of the second window being smaller than the size of the display area; Each image frame of the multi-task animation also includes the display content of the second window; the display content of the second window is displayed on top of the window background; during the display of the multi-task animation, the window background, the display content of the first window, and the display content of the second window all change synchronously.

7. The method according to claim 1 or 2, characterized in that, The method further includes: running a third application in the background, wherein the third window of the third application is not visible; Each image frame of the multi-task animation also includes the display content of the third window, the size of which is equal to the size of the display area; the display content of the third window and the window background do not overlap.

8. An electronic device, characterized in that, The electronic device includes: a processor, a memory, and a communication interface; the memory and the communication interface are coupled to the processor, the memory is used to store computer program code, the computer program code including computer instructions; wherein, when the processor executes the computer instructions, the electronic device performs the method as described in any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions; when the computer instructions are executed on the electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-7.

10. A chip system, characterized in that, The chip system includes a processor and an interface circuit, which are interconnected via a line; wherein the interface circuit is used to receive signals from an electronic device and send the signals to the processor, the signals including computer instructions; when the processor executes the computer instructions, the chip system performs the method as described in any one of claims 1-7.

Images