Application keep-alive method and electronic equipment

Abstract

The invention provides an application keep-alive method and electronic equipment, and relates to the technical field of terminals. And when the electronic equipment is in the non-free screen mode, locking the application in response to the user operation. And after being locked, the application cannot be cleared from the multi-task management interface. And then, the electronic equipment enters a free screen mode, and the locked application is automatically unlocked by the electronic equipment. And after being unlocked, the application can be cleared in the multi-task management interface. Afterwards, the electronic device quits the free screen mode, and due to the fact that the application is cleared, the information of the application does not exist in the multi-task management interface. After the electronic equipment is switched from the non-free screen mode to the free screen mode, the locked application is automatically unlocked by the electronic equipment, so that the problem that the locking rules of a group of applications and a single application are inconsistent due to the fact that the group of applications cannot be locked in the free screen mode is solved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to an application keep-alive method and electronic device. Background Art

[0002] After an application is started on an electronic device, it may be closed by the user or killed by the system according to the system's process management policy.

[0003] Generally speaking, electronic devices such as tablet computers have various application keep-alive strategies. For example, some applications are marked to reduce the probability of these applications being killed by the system. For example, for a specific application, it is periodically woken up so that the specific application is not killed by the system.

[0004] In one implementation, the application may be locked. In some scenarios, the locked application will not be killed by the system, thereby keeping the application alive.

[0005] How to keep applications alive to facilitate user application management is a problem that needs to be solved. Summary of the invention

[0006] The embodiments of the present application provide an application keeping alive method and an electronic device, which can keep applications alive in various scenarios and facilitate users to manage applications.

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

[0008] In a first aspect, a method for keeping an application alive is provided, the method comprising: when the electronic device is in a first mode, displaying a first multi-task management interface, the first multi-task management interface including a first card corresponding to the first application and a second card corresponding to the second application; in response to a lock operation on the first application, displaying a second multi-task management interface, the second multi-task management interface including the first card and a lock mark corresponding to the first application, and also including the second card; after receiving a clear recent task operation from the user on the second multi-task management interface, the second card is cleared from the second multi-task management interface, and the first card and the lock mark corresponding to the first application are not cleared. In response to the user's first operation, displaying a desktop interface of the second mode; that is, the electronic device enters the second mode. In response to the user's second operation, displaying a third multi-task management interface, the third multi-task management interface including a third card corresponding to the first application, and not including a lock mark corresponding to the first application. After receiving a clear recent task operation from the user on the third multi-task management interface, the third card is cleared from the third multi-task management interface. In response to the user's third operation, displaying the desktop interface of the first mode; that is, the electronic device exits the second mode and enters the first mode. In the first mode, in response to a fourth operation of the user, a fourth multi-tasking management interface is displayed, and the fourth multi-tasking management interface does not include a card of the first application.

[0009] In this method, in the non-free screen mode (first mode), after the application is locked in response to a user operation, the electronic device enters the free screen mode (second mode), and the locked application is automatically unlocked by the electronic device. The application can be cleared in the multi-task management interface. Afterwards, the electronic device exits the free screen mode, and since the application has been cleared, the multi-task management interface does not have information about the application. That is, when the electronic device switches from the non-free screen mode to the free screen mode, the locked application is automatically unlocked by the electronic device, avoiding the problem of inconsistent locking rules for a group of applications and a single application due to the inability to lock a group of applications in the free screen mode.

[0010] In combination with the first aspect, in a possible implementation, the method further includes: in the first mode, displaying a fifth multitasking management interface, the fifth multitasking management interface includes a fourth card corresponding to the first application and a fifth card corresponding to the second application; in response to a lock operation on the first application, displaying a sixth multitasking management interface, the sixth multitasking management interface includes a fourth card and a fifth card and a lock mark corresponding to the first application; after receiving a clear recent task operation from the user in the sixth multitasking management interface, the fifth card is cleared from the sixth multitasking management interface, and the fourth card and the lock mark corresponding to the first application are not cleared. In response to the user's fifth operation, displaying the desktop interface of the second mode; that is, entering the second mode. In response to the user's sixth operation, displaying a seventh multitasking management interface, the seventh multitasking management interface includes the sixth card corresponding to the first application, but does not include the lock mark corresponding to the first application. In response to the user's seventh operation, displaying the desktop interface of the first mode; that is, exiting the second mode and entering the first mode. In response to the user's eighth operation, displaying an eighth multitasking management interface, the eighth multitasking management interface includes the seventh card of the first application and the lock mark corresponding to the first application.

[0011] In this method, in the non-free screen mode, after the application is locked in response to a user operation, the electronic device enters the free screen mode, and the locked application is automatically unlocked by the electronic device. Afterwards, the electronic device exits the free screen mode, and the application is automatically locked by the electronic device. In this way, after the electronic device locks the application in response to a user operation, even if a mode change occurs, the information of the locked application will not be lost.

[0012] In combination with the first aspect, in a possible implementation, the method further includes: in the first mode, displaying a ninth multitasking management interface, the ninth multitasking management interface includes an eighth card corresponding to the first application and a ninth card corresponding to the second application; in response to a lock operation on the first application, displaying a tenth multitasking management interface, the tenth multitasking management interface includes an eighth card and a ninth card and a lock mark corresponding to the first application; after receiving a clear recent task operation from the user in the tenth multitasking management interface, the ninth card is cleared from the tenth multitasking management interface, and the eighth card and the lock mark corresponding to the first application are not cleared. In response to the user's ninth operation, displaying a desktop interface of the second mode; that is, entering the second mode. In response to the user's tenth operation, displaying an eleventh multitasking management interface, the eleventh multitasking management interface includes the tenth card corresponding to the first application, but does not include the lock mark corresponding to the first application. In the second mode, the electronic device restarts; after the electronic device restarts, displaying the desktop interface of the first mode; that is, entering the first mode. In response to the user's eleventh operation, displaying a twelfth multitasking management interface, the twelfth multitasking management interface includes the eleventh card corresponding to the first application and the lock mark corresponding to the first application.

[0013] In this method, in the non-free screen mode, after the application is locked in response to a user operation, the electronic device enters the free screen mode, and the locked application is automatically unlocked by the electronic device. Afterwards, the electronic device is restarted, the electronic device enters the non-free screen mode, and the application is automatically locked by the electronic device. In this way, after the electronic device locks the application in response to a user operation, even if an abnormality occurs, such as the electronic device restarting, the information of the locked application will not be lost.

[0014] In combination with the first aspect, in a possible implementation, the method also includes: in the second mode, in response to the user's twelfth operation, displaying a first interface, the first interface including floating windows of multiple applications; in response to the user's thirteenth operation, displaying a thirteenth multi-tasking management interface, the thirteenth multi-tasking management interface including a twelfth card, the twelfth card including thumbnails of the floating windows of the multiple applications.

[0015] In this method, in the free screen mode, the application window is displayed in the form of a floating window. Multiple applications can be displayed as a group.

[0016] In combination with the first aspect, in a possible implementation, the method also includes: in a second mode, displaying a second interface, the bottom task bar of the second interface includes a first application icon; in response to the user dragging the first application icon to a first position on the display screen and releasing it, displaying a floating window of the application indicated by the first application icon at the first position.

[0017] In this method, in the free screen mode, the floating window of the application can be started by dragging the application icon.

[0018] In combination with the first aspect, in a possible implementation, the method also includes: in the second mode, displaying a third interface, the third interface including a first icon; after receiving an operation of the user selecting the first icon, starting multiple applications; and the floating windows of the multiple applications are displayed according to the layout indicated by the first icon.

[0019] In this method, floating windows of multiple applications can be displayed according to a preset layout.

[0020] In combination with the first aspect, in a possible implementation, the method also includes: in the second mode, displaying a fourth interface, the fourth interface including floating windows of multiple applications displayed according to the first layout, the fourth interface also including a second icon, the second icon indicating the second layout; after receiving an operation in which the user selects the second icon, displaying the floating windows of multiple applications according to the second layout.

[0021] In this method, the layout of the floating windows of multiple applications can be conveniently changed by clicking the layout icon.

[0022] In a second aspect, an electronic device is provided, which has the function of implementing the method described in the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0023] In a third aspect, an electronic device is provided, comprising: a processor, a memory and a display screen; the display screen is used to display a user interface, the memory is used to store computer execution instructions, and when the electronic device is running, the processor executes the computer execution instructions stored in the memory to enable the electronic device to perform a method as described in any possible implementation method of the first aspect above.

[0024] In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer can execute the method described in any possible implementation of the first aspect.

[0025] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the method described in any possible implementation of the first aspect.

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

[0027] Figure 1 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0028] Figure 2 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0029] Figure 3 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0030] Figure 4 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0031] Figure 5 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0032] Figure 6 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0033] Figure 7A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0034] Figure 8 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0035] Fig. 9 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0036] Fig.10 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0037] Fig.11 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0038] Fig.12 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0039] Fig.13 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0040] Fig.14 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0041] Fig.15 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0042] Fig.16 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0043] Fig.17 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0044] Fig.18 A schematic diagram of a scenario example of the application keep-alive method provided in an embodiment of the present application;

[0045] Fig.19 A schematic diagram of a flow chart of an application keeping alive method provided in an embodiment of the present application;

[0046] Fig. 20 A schematic diagram of the software structure of an electronic device provided in an embodiment of the present application;

[0047] Fig.21 A schematic diagram of a module interaction timing of the application keep-alive method provided in an embodiment of the present application;

[0048] Fig. 22A schematic diagram of a module interaction timing of the application keep-alive method provided in an embodiment of the present application;

[0049] Fig.23 A schematic diagram of the structural composition of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

[0052] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0053] The application keeping alive method provided in the embodiment of the present application can be applied to electronic devices including display screens. The above electronic devices may include tablet computers, laptop computers, personal computers (PCs), mobile phones, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, smart home devices (e.g., smart TVs, smart screens, large screens, smart speakers, smart air conditioners, etc.), personal digital assistants (PDAs), wearable devices (e.g., smart watches, smart bracelets, etc.), vehicle-mounted devices, virtual reality devices, etc., and the embodiment of the present application does not impose any restrictions on this.

[0054] For example, please refer to Figure 1 , which shows a schematic diagram of the structure of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 130, a display screen 140, a communication module 150, a power module 160, a sensor module 170, etc. Among them, the sensor module 170 may include a pressure sensor, a touch sensor, etc.

[0055] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0056] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), and / or a neural-network processing unit (NPU). Different processing units may be independent components or integrated into one or more processors. In some embodiments, the electronic device 100 may also include one or more processors 110.

[0057] The controller is the nerve center and command center of the electronic device 100. It can generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching and executing instructions.

[0058] The application processor can run the operating system of the electronic device 100, which is used to manage the hardware and software resources of the electronic device 100. For example, it manages and configures memory, determines the priority of system resource supply and demand, controls input and output devices, operates the network, manages the file system, manages drivers, etc. The operating system can also be used to provide an operating interface for users to interact with the system. Among them, various types of software can be installed in the operating system, such as drivers, applications (applications, Apps), etc.

[0059] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0060] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an 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 SIM card interface, and / or a USB interface, etc.

[0061] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0062] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0063] The internal memory 130 can be used to store one or more computer programs, which include instructions. The processor 110 can enable the electronic device 100 to perform the methods provided in some embodiments of the present application, as well as various applications and data management, etc. by running the above instructions stored in the internal memory 130. The internal memory 130 may include a code storage area and a data storage area. Among them, the data storage area can store data created during the use of the electronic device 100, etc. In addition, the internal memory 130 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more disk storage components, a flash memory component, a universal flash storage (UFS), etc. In some embodiments, the processor 110 can enable the electronic device 100 to perform the methods provided in the embodiments of the present application, as well as other applications and data management by running instructions stored in the internal memory 130, and / or instructions stored in a memory provided in the processor 110.

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

[0065] The display screen 140 is used to display images, videos, etc. The display screen 140 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 or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include 1 or N display screens 140, where N is a positive integer greater than 1.

[0066] In some embodiments, the display screen 140 is provided with a pressure sensor, a touch sensor, and the like. The pressure sensor is used to sense pressure signals and can convert pressure signals into electrical signals. When a touch operation is applied to the display screen 140, the electronic device 100 detects the intensity of the touch operation according to the pressure sensor. The electronic device 100 can also calculate the position of the touch according to the detection signal of the pressure sensor. The touch sensor, also known as a "touch panel", can form a touch screen, also known as a "touch screen", with the display screen 140. The touch sensor is used to detect touch operations applied thereto or thereabout. 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 also be provided through the display screen 140.

[0067] The communication module 150 can provide wireless communication solutions including cellular, Wi-Fi, Bluetooth (BT), wireless data transmission modules (e.g., 433MHz, 868MHz, 915MHz), etc. applied to the electronic device 100. The communication module 150 can be one or more devices integrating at least one communication processing module.

[0068] The power module 160 can be used to supply power to various components included in the electronic device 100. In some embodiments, the power module 160 can be a battery, such as a rechargeable battery.

[0069] The following takes a tablet computer as an example of an electronic device to describe in detail the application keeping alive method provided in an embodiment of the present application.

[0070] Generally speaking, tablet computers have a multitasking management interface. The multitasking management interface can also be called a multitasking interface, a background application interface, a Recent interface, etc. The multitasking management interface is used to display information about applications that have been recently launched on the tablet computer, such as application icons, application names, thumbnails, etc.

[0071] When the tablet computer displays any user interface, the multitasking management interface can be opened in response to the user's operation of opening the multitasking management interface. For example, the operation of opening the multitasking management interface may include the user's operation of sliding two fingers from bottom to top on the display screen of the tablet computer; for example, the operation of opening the multitasking management interface may include the user's operation of sliding from bottom to top and pausing on the display screen of the tablet computer; for example, the tablet computer's user interface (such as the bottom navigation bar, the side navigation bar, etc.) includes a Recent key, and the operation of opening the multitasking management interface may include the user's operation of clicking the Recent key.

[0072] In one example, in the startup sequence, application C, application B, and application A are started on the tablet computer 100. In response to the operation of opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 201. For example, Figure 2 As shown in (a), the multitasking management interface 201 includes an icon 2011 of application A, an application name 2012, and a card 2013, for example, the card 2013 includes a thumbnail of the full-screen window of application A; the multitasking management interface 201 also includes an icon 2014 of application B, an application name 2015, and a card 2016, for example, the card 2016 includes a thumbnail of the full-screen window of application B; the multitasking management interface 201 also includes an icon 2017 of application C, an application name 2018, and a card 2019, for example, the card 2019 includes a thumbnail of the full-screen window of application C. In the embodiment of the present application, the application window displayed in full screen is called a full-screen window, and the application window displayed in split screen is called a split screen window.

[0073] The user can open the user interface of any application in the multitasking management interface in the multitasking management interface, and accordingly, the application enters the foreground and runs. For example, in response to the user clicking the thumbnail of the window of application B in the multitasking management interface 201, the electronic device displays the user interface of application B, that is, application B enters the foreground and runs.

[0074] The user can also kill any application in the multitasking management interface. When an application is killed, all processes of the application are cleared from the processor, and the application no longer runs on the electronic device. For example, in response to the user pressing and swiping up on the thumbnail of the window of application C in the multitasking management interface, application C is killed.

[0075] The user can also clear the multitasking management interface, that is, clear the recent tasks (recently opened applications) in the multitasking management interface. In one implementation, in response to the user's operation of clearing the multitasking management interface, the recent tasks in the multitasking management interface are cleared. For example, the multitasking management interface includes a "clear" control, and receiving the user's click operation on the "clear" control means receiving the operation of clearing the multitasking management interface. For example, Figure 2 As shown in (a), the multitasking management interface 201 also includes a "clear" control 202. The user can click the "clear" control 202 to clear the information of application A, application B, and application C from the multitasking management interface 201. For example, Figure 2As shown in (b), in response to the user clicking the "clear" control 202, the tablet computer 100 displays a multitasking management interface 203; there is no relevant information (icons, names, cards) of application A, application B, and application C in the multitasking management interface 203. When the application information is cleared from the multitasking management interface, if the application is running in the background, the application is killed by the system.

[0076] In some embodiments, the tablet computer can lock any application in the multitasking management interface in the multitasking management interface. In one implementation, the tablet computer can lock an application in response to a user's locking operation on an application in the multitasking management interface. For example, the locking operation may include: pressing and holding the card corresponding to the application and pulling it down and then releasing it.

[0077] If an application is locked, when receiving the operation of clearing the multitasking management interface, the locked application will not be cleared from the multitasking management interface, and all applications except the locked application in the multitasking management interface will be cleared. Correspondingly, the locked application will not be killed, that is, by locking the application, the application can be kept alive.

[0078] For example, Figure 3 As shown in (a), the user can perform a lock operation on application A. After receiving the user's lock operation on application A, application A is locked. In one implementation, after application A is locked, a lock mark corresponding to application A is displayed on the multitasking management interface. For example, the lock mark can be a "lock" icon. For example, Figure 3 As shown in (b), the multitasking management interface 201 is updated, and a "lock" icon 2020 is displayed next to the application name 2012 of application A and above the card 2013 in the updated multitasking management interface 201. The "lock" icon 2020 indicates that its corresponding application (application A) has been locked. In other examples, it can be indicated that the application has been locked in other ways, for example, a "lock" icon is displayed on the card of application A, and the text "locked" is displayed next to the name of application A.

[0079] For example, Figure 3 As shown in (c), in response to the user clicking the "clear" control 202, the tablet computer 100 displays the multitasking management interface 204; there is no relevant information (icons, names, cards) of application B and application C in the multitasking management interface 204. The multitasking management interface 204 includes the icon 2011, application name 2012, card 2013 and "lock" icon 2020 of application A. That is, after receiving the user's operation to clear the multitasking management interface, application A is not cleared, and the applications (application B and application C) other than application A in the multitasking management interface are cleared.

[0080] In some embodiments, the tablet computer can unlock the locked application in the multitasking management interface. In one implementation, the tablet computer can unlock the locked application in response to the user's unlocking operation on the locked application. For example, the unlocking operation may include: pressing and holding the card corresponding to the locked application and pulling it down and then releasing it.

[0081] After a locked application is unlocked, the application will be cleared when an operation to clear the multitasking management interface is received.

[0082] For example, Figure 4 As shown in (a) of FIG. 1 , the tablet computer 100 displays a multitasking management interface 204, which includes an icon 2011 of application A, an application name 2012, a card 2013, and a "lock" icon 2020. The user can perform an unlock operation on application A. After receiving the user's unlock operation on application A, application A is unlocked. For example, Figure 4 As shown in (b), the multitasking management interface 204 is updated. In the updated multitasking management interface 204, there is no "lock" icon 2020 next to the application name 2012 of application A and above the card 2013, indicating that application A is not locked.

[0083] For example, Figure 4 As shown in (c), in response to the user clicking the "Clear" control 202, the tablet computer 100 displays the multitasking management interface 205, and the multitasking management interface 205 does not include relevant information of application A (application A's icon 2011, application name 2012, card 2013).

[0084] In some embodiments, the tablet computer includes some special modes, such as free screen mode. Free screen mode may also be referred to as multi-tasking scheduling mode, desktop mode, etc. In the embodiment of the present application, before entering free screen mode or after exiting free screen mode, it is referred to as non-free screen mode. Non-free screen mode may be another special mode, or may not be any special mode. In one example, non-free screen mode may be referred to as the first mode, and free screen mode may be referred to as the second mode.

[0085] The free screen mode is introduced below.

[0086] In one example, if Figure 5 As shown in (a), the tablet computer 100 displays a desktop interface 301 of the non-free screen mode. The desktop interface 301 is the main interface of the non-free screen mode. For example, the desktop interface 301 includes multiple application icons. The desktop interface 301 can also include some cards, such as a weather card, etc. The desktop interface 301 can also include folders, etc.

[0087] The desktop interface 301 may also include one or more bottom navigation bars. Figure 5 As shown in (a), the desktop interface 301 includes a navigation bar 302 and a navigation bar 303; the navigation bar 302 includes multiple application icons, and the application icons in the navigation bar 302 are pre-set. For example, the icons of applications that are frequently used by users can be set in the navigation bar 302; the navigation bar 303 includes multiple application icons, and the navigation bar 303 displays the icons of recently launched applications.

[0088] like Figure 5 As shown in (a), the navigation bar 302 includes a mode switching shortcut icon 304, and the user can operate (eg, click) the mode switching shortcut icon 304 to make the tablet computer 100 enter the free screen mode.

[0089] For example, Figure 5 As shown in (b), in response to the user clicking the mode switching shortcut icon 304, the tablet computer 100 displays the desktop interface 305 of the free screen mode. The desktop interface 305 is the main interface of the free screen mode. For example, the desktop interface 305 includes multiple application icons. The desktop interface 305 may also include some cards, such as weather cards, etc. The desktop interface 305 may also include folders, etc. In an example, the application icons, movies, folders, etc. included in the desktop interface 305 are the same as those of the desktop interface 301.

[0090] The desktop interface 305 may also include one or more bottom navigation bars. Figure 5 As shown in (b), the desktop interface 305 includes a navigation bar 306 and a navigation bar 307; the navigation bar 306 includes multiple application icons, and the application icons in the navigation bar 306 are pre-set. For example, the icons of applications that are frequently used by users can be set in the navigation bar 306; the navigation bar 307 includes multiple application icons, and the navigation bar 307 displays the icons of recently launched applications.

[0091] like Figure 5 As shown in (b), the navigation bar 306 includes a mode switching shortcut icon 308. The user can operate (eg, click) the mode switching shortcut icon 308 to make the tablet computer 100 exit the free screen mode. Figure 5 As shown in (a), in response to the user clicking the mode switching shortcut icon 308, the tablet computer 100 displays the desktop interface 301 of the non-free screen mode.

[0092] Optionally, the navigation bar 306 further includes a “layout” icon 309, and the user can set the layout of the application windows in the free screen mode by operating the “layout” icon 309. The “layout” icon 309 will be described in detail later.

[0093] Generally speaking, in non-free screen mode, there can be one application window displayed in full screen on the desktop, or multiple application windows displayed in split screen.

[0094] Take the full screen display of application windows as an example. If you start application A, application B, and application C in sequence in non-free screen mode, you can start application A first, and the tablet displays the window of application A; then start application B, the tablet displays the window of application B, and closes the window of application A; then start application C, the tablet displays the window of application C, and closes the window of application B.

[0095] Multiple application windows can also be displayed in split screens. For example, when application D and application E are started in non-free screen mode, application D and application E are displayed in split screens.

[0096] In one example, in the non-free screen mode, the applications running in the tablet computer include application A, application B, application C, application D, and application E.

[0097] For example, Figure 6 As shown, the tablet computer 100 displays a desktop interface 301 in a non-free screen mode, and the tablet computer 100 runs applications A, B, C, D, and E. In response to the user's operation of opening the multitasking management interface, the tablet computer 100 displays a multitasking management interface 401, which includes relevant information (icons, names, cards) of applications A, B, C, D, and E. Optionally, applications D and E are displayed in split screens, and accordingly, the card sizes of applications D and E in the multitasking management interface 401 are half of that of application A (or application B or application C). In one implementation, each application in the multitasking management interface 401 corresponds to a card.

[0098] After that, the tablet computer enters the free screen mode, for example, when receiving a user's Figure 6 After clicking the mode switching shortcut icon 304 on the desktop interface 301, Figure 7 As shown in (a), the tablet computer 100 displays the desktop interface 305 in the free screen mode. In response to the user opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 402, which includes relevant information of application A, application B, application C, application D, and application E. In one implementation, Figure 7As shown in (b), the multitasking management interface 402 includes card 4021, card 4022, card 4023 and card 4024, wherein card 4021 includes a thumbnail of a floating window of application A, card 4022 includes a thumbnail of a floating window of application B, card 4023 includes a thumbnail of a floating window of application C, and card 4024 includes thumbnails of floating windows of application D and application E. That is, each card corresponds to all applications displayed on the screen at the same time.

[0099] In free screen mode, the tablet computer can display floating windows of multiple applications on one screen, and the multiple applications are a group. In one implementation, when the tablet computer is in free screen mode, after the tablet computer displays the desktop interface, multiple applications are started through the desktop interface, wherein the window of each application is displayed as a floating window, and the multiple applications are a group. After the tablet computer exits the desktop interface and enters the desktop interface again, another group of applications can be started. That is, the applications started between the tablet computer entering the desktop interface and exiting the desktop interface are a group of applications. Among them, the window size of the floating window is smaller than the full screen, and the display position of the floating window can be moved in response to the user's dragging operation on the floating window, and a floating window can cover part of other windows.

[0100] For example, Figure 7 As shown in (a), the tablet computer 100 displays a desktop interface 305 in a free screen mode, and the user can start one or more applications through the desktop interface 305. For example, the user can click on an application icon on the desktop interface 305 to start the corresponding application, the user can click on an application icon in the navigation bar 306 on the desktop interface 305 to start the corresponding application, the user can click on an application icon in the navigation bar 307 on the desktop interface 305 to start the corresponding application, and the user can click on an application icon in the side navigation bar on the desktop interface 305 to start the corresponding application, etc. Optionally, the user can also press and hold an application icon in the navigation bar 306 or 307 and drag the application icon, and then release the application icon at any position in the desktop interface 305, and accordingly, a floating window of the application is displayed at the position where the application icon is released.

[0101] In one example, the user starts application F, application G, and application H through the desktop interface 305, for example, Figure 8 As shown in (a), the tablet computer 100 displays a user interface 310, which includes a window 311 of application F, a window 312 of application G, and a window 313 of application H. Window 311, window 312, and window 313 are all floating windows.

[0102] Afterwards, in response to the user opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 403, which includes relevant information of application A, application B, application C, application D, application E, application F, application G, and application H. In one implementation, Figure 8 As shown in (b), the multitasking management interface 403 includes card 4031, card 4032, card 4033, card 4034 and card 4035, wherein card 4031 includes a thumbnail of a floating window of application A, card 4032 includes a thumbnail of a floating window of application B, card 4033 includes a thumbnail of a floating window of application C, card 4034 includes thumbnails of floating windows of application D and application E, and card 4035 includes thumbnails of floating windows of application F, application G and application H. That is, each card corresponds to all applications displayed on the screen at the same time.

[0103] In some embodiments, in the free screen mode, multiple floating windows in a group can be laid out, and the display positions and areas of multiple floating windows in a group of applications can be set.

[0104] In some examples, such as Fig. 9 As shown in (a), the tablet computer 100 displays a desktop interface 305 in the free screen mode. The desktop interface 305 is the main interface of the free screen mode. The navigation bar 306 of the desktop interface 305 includes a "layout" icon 309. Fig. 9 As shown in (b), in response to the user clicking the "Layout" icon 309, the tablet computer 100 displays the "Quick Layout" interface 320, which includes multiple layout templates, each of which defines a layout format of multiple windows of a group of applications. Exemplarily, the "Quick Layout" interface 320 includes a layout template 3201.

[0105] In one example, if Fig.10 As shown in (a), in response to a user clicking operation on the layout template 3201, the tablet computer displays a user interface 330, and the user interface 330 includes area 1, area 2, and area 3, and the layout format of area 1, area 2, and area 3 is the same as the layout format indicated by the layout template 3201.

[0106] Illustratively, the bottom navigation bar of user interface 330 includes an icon 3301 of application F, an icon 3302 of application G, and an icon 3303 of application H.

[0107] In one implementation, the user can start application F by clicking icon 3301, start application G by clicking icon 3302, and start application H by clicking icon 3303. Tablet computer 100 displays the window of application F in area 1, the window of application G in area 2, and the window of application H in area 3 in the order in which application F, application G, and application H are started.

[0108] In another implementation, the user can press and drag the icon 3301 of application F and release icon 3301 in area 1, so that the tablet computer 100 displays the window of application F in area 1; the user can press and drag the icon 3302 of application G and release icon 3302 in area 2, so that the tablet computer 100 displays the window of application G in area 2; the user can press and drag the icon 3303 of application H and release icon 3303 in area 3, so that the tablet computer 100 displays the window of application H in area 3.

[0109] For example, Fig.10 As shown in (b), the tablet computer 100 displays a user interface 340, which includes floating windows of application F, application G, and application H, wherein the window of application F is displayed in area 1, the window of application G is displayed in area 2, and the window of application H is displayed in area 3.

[0110] In other examples, such as Fig.11 As shown in (a), the tablet computer 100 displays a user interface 310, which includes a window 311 of application F, a window 312 of application G, and a window 313 of application H. The bottom navigation bar of the user interface 310 also includes a "layout" icon 314. Fig.11 As shown in (b), in response to the user clicking the "Layout" icon 314 in the user interface 310, the tablet computer 100 displays a "Quick Layout" interface 350, and the "Quick Layout" interface 350 includes multiple layout templates, each layout template defines a layout format of multiple windows of a group of applications; exemplarily, the "Quick Layout" interface 350 includes a layout template 3501.

[0111] In one implementation, Fig.12 As shown in (a), in response to a user clicking operation on the layout template 3501, the tablet computer 100 displays a user interface 360, which includes area 1, area 2, and area 3. The layout formats of area 1, area 2, and area 3 are the same as the layout format indicated by the layout template 3501. Among them, area 1 includes thumbnails of floating windows of application F, application G, and application H.

[0112] The user can press and drag the thumbnail of the floating window of application F, and release the thumbnail of the floating window of application F in area 1, so that the tablet computer 100 displays the window of application F in area 1; the user can press and drag the thumbnail of the floating window of application G, and release the thumbnail of the floating window of application G in area 2, so that the tablet computer 100 displays the window of application G in area 2; the user can press and drag the thumbnail of the floating window of application H, and release the thumbnail of the floating window of application H in area 3, so that the tablet computer 100 displays the window of application H in area 3. For example, Fig.12 As shown in (b), the tablet computer 100 displays a user interface 370, which includes floating windows of application F, application G, and application H, wherein the window of application F is displayed in area 1, the window of application G is displayed in area 2, and the window of application H is displayed in area 3.

[0113] In another implementation, in response to a user clicking operation on the layout template 3501, the tablet computer 100 displays a user interface 370, the user interface 370 includes area 1, area 2, and area 3, and the layout format of area 1, area 2, and area 3 is the same as the layout format indicated by the layout template 3501; the tablet computer 100 displays the window of application F in area 1, the window of application G in area 2, and the window of application H in area 3 according to a preset strategy (for example, according to the startup order of the applications).

[0114] In other examples, such as Fig.13 As shown in (a) of FIG. 1 , the tablet computer 100 displays a user interface 380 , which includes area 1 , area 2 , and area 3 . The window of application F is displayed in area 1 , the window of application G is displayed in area 2 , and the window of application H is displayed in area 3 .

[0115] The bottom navigation bar of the user interface 380 includes a "layout" icon 3801. In response to the user clicking the "layout" icon 3801, the tablet computer 100 displays a "quick layout" interface 381, which includes multiple layout templates, each of which defines a layout format of multiple windows of a group of applications. Exemplarily, the "quick layout" interface 381 includes a layout template 3811 and a layout template 3812. The layout formats of regions 1, 2, and 3 in the user interface 380 are the same as the layout format indicated by the layout template 3811.

[0116] like Fig.13As shown in (b), in response to the user clicking on the layout template 3812, the tablet computer 100 displays the user interface 390, which includes area 4, area 5, and area 6. The layout formats of area 4, area 5, and area 6 are the same as the layout format indicated by the layout template 3812. The window of application F is displayed in area 4, the window of application G is displayed in area 5, and the window of application H is displayed in area 6.

[0117] In this method, in the free screen mode, the user can easily change the layout format of multiple floating windows in a group of applications.

[0118] In some embodiments, in non-free screen mode, the tablet computer can lock or unlock an application in the multi-tasking management interface. When the tablet computer enters the free screen mode from the non-free screen mode, if there are locked applications, since the tablet computer cannot lock or unlock a group of applications, it will cause the problem of inconsistent locking and unlocking rules for a single application and a group of applications. In an embodiment of the present application, when the tablet computer enters the free screen mode from the non-free screen mode, the tablet computer uniformly unlocks all locked applications. In this way, it is possible to avoid the confusion caused by some applications being able to be locked and some applications being unable to be locked in the free screen mode, because a single application can be locked and a group of applications cannot be locked.

[0119] In one example, in the non-free screen mode, the tablet computer 100 starts application C, application B, and application A in sequence. Fig.14 As shown in (a), in response to the user's operation of opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 501, and the multitasking management interface 501 includes an icon 5011 of application A, an application name 5012, and a card 5013, for example, card 5013 includes a thumbnail of the full-screen window of application A; the multitasking management interface 501 also includes an icon 5014 of application B, an application name 5015, and a card 5016, for example, card 5016 includes a thumbnail of the full-screen window of application B; the multitasking management interface 501 also includes an icon 5017 of application C, an application name 5018, and a card 5019, for example, card 5019 includes a thumbnail of the full-screen window of application C. Among them, a "lock" icon 502 is displayed next to the application name 5012 of application A and above the card 5013 in the multitasking management interface 501. The "lock" icon 502 indicates that its corresponding application (application A) has been locked. Exemplarily, Fig.14 In (a) the multi-task management interface 501 may be Figure 3 (b) The multi-tasking management interface 201.

[0120] After application A has been locked, when the user clears the multitasking management interface, application A will not be cleared. Figure 3 .

[0121] In some examples, when application A, application B, and application C are running on the tablet computer 100, the tablet computer 100 enters the free screen mode. Fig.14 As shown in (b), the tablet computer 100 displays a desktop interface 503 in a non-free screen mode, and the desktop interface 503 includes a navigation bar 504, and the navigation bar 504 includes a mode switching shortcut icon 5041. For example, Fig.14 As shown in (c), in response to the user clicking the mode switching shortcut icon 5041, the tablet computer 100 displays the desktop interface 505 of the free screen mode. For example, the desktop interface 505 includes a navigation bar 506, and the navigation bar 506 includes a mode switching shortcut icon 5061 and a "layout" icon 5062, etc.

[0122] In the free screen mode, in response to the user opening the multitasking management interface, such as Fig.14 As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes an icon 5071 of application A, an application name 5072, and a card 5073, wherein the card 5073 includes a thumbnail of a floating window of application A; the multitasking management interface 507 also includes an icon 5074 of application B, an application name 5075, and a card 5076, wherein the card 5076 includes a thumbnail of a floating window of application B; the multitasking management interface 507 also includes an icon 5077 of application C, an application name 5078, and a card 5079, wherein the card 5079 includes a thumbnail of a floating window of application C. Among them, application A has been unlocked, and the multitasking management interface 507 does not include a "lock" icon corresponding to application A.

[0123] After application A has been unlocked (application A is not locked), when the user clears the multitasking management interface, application A will be cleared. Fig.15 As shown in (a), the multitasking management interface 507 also includes a "clear" control 508. The user can click the "clear" control 508 to kill application A, application B, and application C. Fig.15 As shown in (b), in response to the user clicking the "Clear" control 508, the tablet computer 100 displays a multitasking management interface 509; there is no relevant information (icons, names, cards) of application A, application B and application C in the multitasking management interface 509.

[0124] Afterwards, the tablet computer 100 exits the free screen mode. Fig.15As shown in (c), the tablet computer 100 displays a desktop interface 510 in the free screen mode, and the desktop interface 510 includes a navigation bar 520, and the navigation bar 520 includes a mode switching shortcut icon 5201 and a "layout" icon 5202. For example, Fig.15 As shown in (d), in response to the user clicking the mode switching shortcut icon 5201, the tablet computer 100 displays the desktop interface 530 of the non-free screen mode.

[0125] In the non-free screen mode, in response to the user opening the multi-task management interface, such as Fig.15 As shown in (e), the tablet computer 100 displays a multitasking management interface 540, and there is no relevant information (icons, names, cards) of application A, application B, and application C in the multitasking management interface 540.

[0126] In this embodiment, in the non-free screen mode, after locking the application in response to the user operation, the tablet computer enters the free screen mode, and the locked application is automatically unlocked by the tablet computer. The application can be killed in the multi-task management interface. After that, the tablet computer exits the free screen mode, and since the application has been cleared, there is no information about the application in the multi-task management interface. That is, when the tablet computer switches from the non-free screen mode to the free screen mode, the locked application is automatically unlocked by the tablet computer, avoiding the problem of inconsistent locking rules of a group of applications and a single application due to the inability to lock a group of applications in the free screen mode.

[0127] In some embodiments, after the tablet computer enters the free screen mode from the non-free screen mode, the information of the locked applications is saved, and then the locked applications are unlocked. Afterwards, when the tablet computer exits the free screen mode and enters the non-free screen mode, the applications are locked according to the saved information of the locked applications. In this way, the locked applications can be prevented from losing their locked state after the tablet computer switches modes.

[0128] In one example, if Fig.14 In the example shown, in the non-free screen mode, application C, application B, and application A are started on the tablet computer 100 in sequence. In response to the user opening the multitasking management interface, the tablet computer 100 displays a multitasking management interface 501. The multitasking management interface 501 includes relevant information (icons, names, cards, etc.) of application A, application B, and application C. The multitasking management interface 501 also includes a "lock" icon 502 corresponding to application A, which means that application A has been locked. Afterwards, the tablet computer 100 enters the free screen mode. In the free screen mode, in response to the user opening the multitasking management interface, such as Fig.14As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes relevant information (icons, names, cards, etc.) of application A, application B, and application C. The multitasking management interface 507 does not include a "lock" icon corresponding to application A.

[0129] Afterwards, the tablet computer 100 exits the free screen mode. Fig.16 As shown in (a), the tablet computer 100 displays a desktop interface 550 in the free screen mode, and the desktop interface 550 includes a navigation bar 560, and the navigation bar 560 includes a mode switching shortcut icon 5601 and a "layout" icon 5602. For example, Fig.16 As shown in (b), in response to the user clicking the mode switching shortcut icon 5601, the tablet computer 100 displays the desktop interface 570 of the non-free screen mode.

[0130] In the non-free screen mode, in response to the user opening the multi-task management interface, such as Fig.16 As shown in (c), the tablet computer 100 displays a multitasking management interface 580, which includes an icon 5801 of application A, an application name 5802, and a card 5803. For example, card 5803 includes a thumbnail of a full-screen window of application A. The multitasking management interface 580 also includes an icon 5804 of application B, an application name 5805, and a card 5806. For example, card 5806 includes a thumbnail of a full-screen window of application B. The multitasking management interface 580 also includes an icon 5807 of application C, an application name 5808, and a card 5809. For example, card 5809 includes a thumbnail of a full-screen window of application C. Among them, a "lock" icon 590 is displayed next to the application name 5802 of application A and above the card 5803 in the multitasking management interface 580. The "lock" icon 590 indicates that its corresponding application (application A) has been locked. Exemplarily, Fig.16 (c) The multitasking management interface 580 can be used with Fig.14 The multi-tasking management interface 501 in (a) is the same.

[0131] In another example, Fig.14 In the example shown, in the non-free screen mode, application C, application B, and application A are started on the tablet computer 100 in sequence. In response to the user opening the multitasking management interface, the tablet computer 100 displays a multitasking management interface 501. The multitasking management interface 501 includes relevant information (icons, names, cards, etc.) of application A, application B, and application C. The multitasking management interface 501 also includes a "lock" icon 502 corresponding to application A, which means that application A has been locked. Afterwards, the tablet computer 100 enters the free screen mode. In the free screen mode, in response to the user opening the multitasking management interface, such as Fig.14As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes relevant information (icons, names, cards, etc.) of application A, application B, and application C. The multitasking management interface 507 does not include a "lock" icon corresponding to application A.

[0132] Afterwards, if Fig.17 As shown in (a), when the tablet computer 100 displays the multitasking management interface 507, after receiving the user's click operation on the thumbnail of the floating window of application A in card 5073, application A is called to run in the foreground. Fig.17 As shown in (b), in response to a click operation on the thumbnail of the floating window of application A in card 5073, the tablet computer 100 displays a user interface 601, which includes a floating window 602 of application A. Optionally, the user interface 601 includes a navigation bar 603, and the navigation bar 603 includes an application icon 6031. Fig.17 As shown in (c), in response to the user pressing and dragging the application icon 6031 and releasing it at a position on the screen, the tablet computer 100 displays a user interface 604, which includes a floating window 602 of application A and a floating window 605 of application F. Optionally, the floating window 605 of application F is displayed at a position where the user presses and drags the application icon 6031 and releases it on the screen.

[0133] Afterwards, if Fig.17 As shown in (d), in response to the user's operation of opening the multitasking management interface, the tablet computer 100 displays a multitasking management interface 606, which includes an icon 6061 of application A, an icon 6062 of application F, a name 6063 of application A, a name 6064 of application F, and a card 6065, wherein the card 6065 includes thumbnails of floating windows of application A and application F, and the multitasking management interface 606 also includes an icon 6066 of application B, a name 6067 of application B, and a card 6068 (including a thumbnail of a floating window of application B). The multitasking management interface 606 also includes an icon 6069 of application C, a name 606a of application C, and a card 606b (including a thumbnail of a floating window of application C). Among them, the card 6065 includes thumbnails of floating windows of application A and application F, indicating that application A and application F are a group of applications. The "lock" icon corresponding to application A is not included in the multitasking management interface 606, indicating that application A has been unlocked.

[0134] After that, the tablet computer 100 exits the free screen mode. For example, the tablet computer 100 can exit the free screen mode and enter the non-free screen mode by clicking the mode switching shortcut icon. The process is not illustrated in detail here. In the non-free screen mode, in response to the user's operation of opening the multitasking management interface, such as Fig.17As shown in (e), the tablet computer 100 displays a multitasking management interface 607, which includes an icon 6071, a name 6072, and a card 6073 (including a thumbnail of the full-screen window of application A) of application A, an icon 6074, a name 6075, and a card 6076 (including a thumbnail of the full-screen window of application B) of application B, an icon 6077, a name 6078, and a card 6079 (including a thumbnail of the full-screen window of application C) of application C, and an icon 6081, a name 6082, and a card 6083 (including a thumbnail of the full-screen window of application F) of application F. Among them, a "lock" icon 609 is displayed next to the name 6072 of application A and above the card 6073, indicating that application A has been locked. That is, after exiting the free screen, the application that has been locked before entering the free screen is automatically locked by the tablet computer.

[0135] In this embodiment, in the non-free screen mode, after locking the application in response to a user operation, the tablet computer enters the free screen mode, and the locked application is automatically unlocked by the tablet computer. Afterwards, the tablet computer exits the free screen mode, and the application is automatically locked by the tablet computer. In this way, after the tablet computer locks the application in response to a user operation, even if a mode change occurs, the information of the locked application will not be lost.

[0136] In some embodiments, in the non-free screen mode, the application is locked; then the tablet enters the free screen mode, and the locked application is unlocked by the tablet. If the tablet is restarted or the system is restarted in the free screen mode, the tablet will enter the non-free screen mode after the restart, and the tablet will automatically lock the applications that were locked before entering the free screen mode (these applications have been unlocked after entering the free screen mode).

[0137] Exemplary, reference Fig.14 In the non-free screen mode, the tablet computer 100 has successively started application C, application B and application A. In response to the user's operation of opening the multitasking management interface, the tablet computer 100 displays a multitasking management interface 501. The multitasking management interface 501 includes relevant information (icons, names, cards, etc.) of application A, application B and application C. The multitasking management interface 501 also includes a "lock" icon 502 corresponding to application A, that is, application A has been locked. Afterwards, the tablet computer 100 enters the free screen mode. In the free screen mode, in response to the user's operation of opening the multitasking management interface, such as Fig.14 As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes relevant information (icons, names, cards, etc.) of application A, application B, and application C. The multitasking management interface 507 does not include a "lock" icon corresponding to application A.

[0138] If the tablet computer 100 is restarted or the system of the tablet computer 100 is restarted, the tablet computer 100 is in the non-free screen mode after the restart, and the application A is locked by the tablet computer 100. For example, Fig.18 As shown in (a), the tablet computer 100 displays the multitasking management interface 507. Afterwards, the tablet computer 100 restarts, as shown in FIG. Fig.18 As shown in (b), after the tablet computer 100 is restarted, the desktop interface 701 of the non-free screen mode is displayed. Fig.18 As shown in (c), in response to the user opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 501, and the multitasking management interface 501 includes a "lock" icon 502 corresponding to application A.

[0139] For example, Fig.19 As shown, the application keep-alive method provided in the embodiment of the present application may include:

[0140] S801. The tablet computer locks any one or more applications in the non-free screen mode, and writes application information of the locked applications into a keep-alive list.

[0141] For example, in the non-free screen mode, the user can perform a lock operation on any one of the applications in the multi-task management interface. The tablet computer locks the application in response to the user's lock operation in the multi-task management interface. Figure 3 As shown in (a), the user performs a lock operation on application A in the multitasking management interface 201. Figure 3 As shown in (b) , a “lock” icon 2020 is displayed above the card 2013 of application A.

[0142] The keep-alive list is used to store locked application information. For example, the application information may include the package name of the application, the identifier of the application, and the like.

[0143] When you clear the apps in the multitasking management interface, the apps included in the keep-alive list will not be cleared.

[0144] S802. The tablet computer enters the free screen mode, saves all application information in the keep-alive list to the backup list, unlocks the applications included in the keep-alive list, and clears the keep-alive list.

[0145] For example, Figure 5 As shown in (a), the desktop interface 301 of the non-free screen mode includes a mode switching shortcut icon 304. After receiving a click operation on the mode switching shortcut icon 304 by the user, the tablet computer 100 enters the free screen mode.

[0146] S803: The tablet computer enters a non-free screen mode, locks the applications included in the backup list, writes application information of the locked applications into a keep-alive list, and clears the backup list.

[0147] In one scenario, the tablet computer exits the free screen mode and enters the non-free screen mode. Fig.15 As shown in (c), the tablet computer 100 displays a desktop interface 510 in the free screen mode, and the desktop interface 510 includes a mode switching shortcut icon 5201. After receiving a click operation on the mode switching shortcut icon 5201 by the user, the tablet computer 100 exits the free screen mode.

[0148] In another scenario, when in the free screen mode, the tablet computer is restarted, or the system of the tablet computer is restarted, and after the tablet computer is restarted, or after the system of the tablet computer is restarted, the tablet computer enters the non-free screen mode.

[0149] After the tablet enters the non-free screen mode, the applications included in the backup list are locked, and the application information of the locked applications is written into the keep-alive list. In this way, when the applications are cleared in the multitasking management interface, the applications included in the keep-alive list will not be cleared.

[0150] In this embodiment, when the tablet computer enters the free screen mode from the non-free screen mode, all locked applications are unlocked, so that in the free screen mode, all applications are unlocked. In addition, before clearing the keep-alive list, the information in the keep-alive list is saved to the backup list, and the backup list can be used to lock the application when entering the non-free screen mode. When the tablet computer enters the non-free screen mode from the free screen mode, the applications included in the backup list are locked, and the locked application information is saved to the keep-alive list, so that after exiting the free screen mode, the application is automatically locked, and the locked application information will not be lost.

[0151] The application keeping alive method provided in the embodiment of the present application can be applied to an electronic device including a display screen. In the embodiment of the present application, the electronic device is an electronic device that can run an operating system and install an application program. Optionally, the operating system running on the electronic device can be system, system, System, etc.

[0152] The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. Taking the system as an example, the software structure of the electronic device 100 is exemplified.

[0153] Fig. 20 It is a schematic diagram of a software structure of the electronic device 100.

[0154] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. The system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system library, and kernel layer.

[0155] The application layer may include a series of application packages, such as desktop applications, system UI applications, etc.

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

[0157] like Fig. 20 As shown, the application framework layer may include a window management module, a content provider module, a view system, a resource management module, an input management module, and the like.

[0158] The window management module is used to manage window programs. The window management module can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0159] The content provider module is used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

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

[0161] The resource management module provides various resources for the application, such as localized strings, icons, images, layout files, video files, etc.

[0162] The input management module is used to process input information. For example, the input information may be input by a user to the electronic device 100 through a keyboard, input by a user to the electronic device 100 through a touch screen, or input to the electronic device 100 through a sensor.

[0163] Android Runtime includes core libraries and virtual machines. Android runtime is responsible for Scheduling and management of the system.

[0164] The core library consists of two parts: one is the function that the Java language needs to call, and the other is The core library.

[0165] The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0166] The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

[0167] The kernel layer is the layer between hardware and software. The kernel layer can contain display drivers, sensor drivers, etc.

[0168] Combine the following Fig. 20 The application keep-alive method provided in the embodiment of the present application is introduced.

[0169] For example, Fig.21 As shown, the application keep-alive method provided in the embodiment of the present application may include:

[0170] S2101. The input management module receives a lock operation event for application 1, and sends the lock operation event to a desktop application.

[0171] The lock operation event includes information about the application that performs the lock operation, such as the application package name.

[0172] S2102. The desktop application locks application one.

[0173] For example, the multitasking management interface is updated, and the updated multitasking management interface displays a "lock" icon corresponding to the application.

[0174] S2103. The desktop application notifies the system interface application that application 1 has been locked.

[0175] S2104. The system interface application writes the application information of application 1 into the keep-alive list.

[0176] In this way, when you clear the application in the multitasking management interface, application 1 will not be cleared.

[0177] In the non-free screen mode, the tablet computer can execute S2101-S2104 multiple times to lock multiple applications respectively.

[0178] Afterwards, the application keep-alive method provided in the embodiment of the present application may further include:

[0179] S2111. The input management module receives an operation event of entering the free screen mode, and notifies the desktop application to enter the free screen mode.

[0180] S2112. The desktop application notifies the system interface application to enter free screen mode.

[0181] The system interface application switches the tablet to free screen mode. In free screen mode, the application window is displayed as a floating window.

[0182] S2113. The system interface application notifies the desktop application that it has entered free screen mode.

[0183] S2114. The desktop application obtains a keep-alive list from the system interface application.

[0184] S2115. The desktop application saves all application information in the keep-alive list to the backup list.

[0185] S2116. The desktop application unlocks the applications included in the keep-alive list and notifies the system interface application to clear the keep-alive list.

[0186] After unlocking an app, the "lock" icon corresponding to the app will not be displayed in the multitasking management interface.

[0187] S2117. Clear the keep-alive list in the system interface application.

[0188] Afterwards, in one scenario, when the tablet computer is in the free screen mode, in response to the user's operation of exiting the free screen mode, the tablet computer exits the free screen mode. Exemplarily, the application keeping alive method provided in the embodiment of the present application may also include:

[0189] S2121: The input management module receives an operation event for exiting the free screen mode, and notifies the desktop application to exit the free screen mode.

[0190] S2122. The desktop application notifies the system interface application to exit the free screen mode.

[0191] The system interface application switches the tablet to non-free screen mode.

[0192] S2123. The system interface application notifies the desktop application that it has exited the free screen mode.

[0193] S2124: The desktop application locks the applications included in the backup list.

[0194] After locking an application, a "lock" icon corresponding to the application will be included in the multitasking management interface.

[0195] S2125. The desktop application notifies the system interface application to write application information of the locked application into a keep-alive list.

[0196] S2126. The system interface application writes the application information of the locked application into the keep-alive list.

[0197] S2127. Clear the backup list in the desktop application.

[0198] In another scenario, when the tablet computer is in free screen mode, the tablet computer restarts to restart the system, or the tablet computer system restarts. After the system restarts, the tablet computer enters non-free screen mode. Exemplarily, the application keeping alive method provided in the embodiment of the present application may also include:

[0199] S2131. After the system restarts, the desktop application creates a desktop interface. When creating the desktop interface, the desktop application queries the system interface application for the current mode of the tablet computer. After the system restarts, the current mode of the tablet computer is a non-free screen mode.

[0200] S2132: The desktop application locks the applications included in the backup list.

[0201] When the backup list includes at least one application information, the desktop application locks the application included in the backup list.

[0202] The backup list includes at least one application information, indicating that the tablet computer is in free screen mode before the system is restarted, and at least one application has been locked before the tablet computer enters the free screen mode, and these applications have been unlocked after the tablet computer enters the free screen mode. After the tablet computer system is restarted and enters the non-free screen mode, these applications need to be locked.

[0203] S2133. The desktop application notifies the system interface application to write application information of the locked application into a keep-alive list.

[0204] S2134. The system interface application writes the application information of the locked application into the keep-alive list.

[0205] S2135. The desktop application clears the backup list.

[0206] In another scenario, when the tablet is in free screen mode, the desktop process restarts. After the desktop process restarts, the tablet enters free screen mode. In this scenario, after the desktop process restarts, the desktop application creates a desktop interface. When creating the desktop interface, the desktop application queries the system interface application for the current mode of the tablet. After the desktop process restarts, the current mode of the tablet is free screen mode. The mode of the tablet does not change, and the tablet does not need to lock or unlock the application.

[0207] It can be understood that the desktop application and the system interface application include multiple sub-modules (classes) and are executed on the tablet computer. Fig.21 During each step shown, each class of the desktop application and each class of the system interface application executes corresponding logic.

[0208] In one example, the desktop application includes Launcher (desktop main process class), HnDesktopVisibilityController (desktop visibility control class), Hotseat switch (hot key switch), Taskbar (bottom taskbar), SystemUIProxy (system UI proxy class), TaskViewHeader (task icon class), HnRecentsLockUtils (addition and unlocking method class), etc.

[0209] System interface applications include HwRecentsLockProvider (lock and unlock data interface class), DesktopTaskController (desktop task control class), etc.

[0210] Among them, Launcher (desktop main process class) is the main process of the desktop application.

[0211] HnDesktopVisibilityController (desktop visibility control class) is used to control the visibility of elements on the desktop interface; for example, after opening a new application window on the desktop interface, the desktop elements outside the application window are cleared; for example, entering the free screen mode makes the application window in the free screen mode visible, and exiting the free screen mode makes the application window in the non-free screen mode visible.

[0212] Hotseat switch (hot key switch), also known as bottom Dock bar, bottom application launch bar. Hotseat switch is used to control the bottom application launch bar in non-free screen mode. For example, the Hotseat switch receives the operation of entering free screen mode.

[0213] Taskbar (bottom taskbar) is used to control the bottom application launch bar in free screen mode. For example, Taskbar receives the operation of exiting free screen mode.

[0214] SystemUIProxy (system UI proxy class) is used to manage interfaces called across processes, such as those called by SystemUI or system interfaces called indirectly through SystemUI.

[0215] TaskViewHeader (task icon class) is used to manage the application icons, application names, "lock" icons, etc. displayed in the multi-task management interface.

[0216] HnRecentsLockUtils (lock and unlock method class) is used to manage the process of locking or unlocking applications in the multi-tasking management interface.

[0217] HwRecentsLockProvider (lock and unlock data interface class), an operation class provided by the SystemUI database to the outside world, used to write data to the SystemUI database or read data from the SystemUI database.

[0218] DesktopTaskController (desktop task control class) is used to control entry or exit of free screen mode; it is also used to implement free screen mode. For example, after the free screen mode detects that the application is opened as a full-screen window or a split-screen window, the application window is converted into a floating window, for example, to manage the number of applications opened in the foreground.

[0219] For example, Fig. 22 As shown, the application keep-alive method provided in the embodiment of the present application may include:

[0220] S2201: The task icon class receives a lock operation event for application one.

[0221] In one example, the display screen receives an operation of a user pressing and releasing a card corresponding to application 1 in the multitasking management interface, and the display driver generates a lock operation event. After receiving the lock operation event, the task icon class determines that a lock operation event for application 1 has been received.

[0222] S2202: The task icon class locks application one.

[0223] In one example, the task icon class displays a “lock” icon corresponding to an application in the multi-task management interface.

[0224] S2203. The task icon class calls the lock and unlock method class to save the information of application one.

[0225] S2204. The encryption and unlocking method class calls the encryption and unlocking data interface class to save the information of application one to the database of the system interface application.

[0226] In one implementation, the database of the system interface application includes a keep-alive list, which includes one or more application information (such as application package name, application identifier, etc.) When the application is locked, the application information of the locked application is written into the keep-alive list.

[0227] In the non-free screen mode, the tablet computer can execute S2201-S2204 multiple times to lock multiple applications respectively.

[0228] Afterwards, the application keep-alive method provided in the embodiment of the present application may further include:

[0229] S2211. The hot key switch receives an operation event for entering the free screen mode.

[0230] For example, when a desktop interface in a non-free screen mode is displayed, the display screen receives a user click operation on a mode switching shortcut icon in a navigation bar of the desktop interface, and accordingly, the hot key switch receives an operation event to enter the free screen mode.

[0231] S2212. The hot key switch calls the system UI proxy class to enter the free screen mode.

[0232] S2213. The system UI proxy class calls the desktop task control class to enter the free screen mode.

[0233] S2214. The desktop task control class calls the desktop visibility control class to notify the desktop application that it has entered the free screen mode.

[0234] S2215. The desktop visibility control class calls the unlock method class and sends a mode change indication message.

[0235] In one implementation, the mode change indication information is a first value, indicating entering the free screen mode.

[0236] S2216, the unlock method class calls the unlock data interface class to obtain application information of the locked application, and saves the application information of the locked application in the storage file of the desktop application. The unlock method class calls the unlock data interface class to unlock the locked application and clear the keep-alive list.

[0237] The lock / unlock method class determines to enter the free screen mode according to the mode change indication information, and calls the lock / unlock data interface class to obtain the application information of the locked application. In one implementation, the lock / unlock data interface is called to obtain the keep-alive list in the database of the system interface application, and the application information of the locked application is obtained according to the keep-alive list.

[0238] The locking and unlocking method class saves the application information of the locked application in the storage file of the desktop application. For example, the storage file is a backup list. In one implementation method, the application information of the locked application is saved in the DESKTOP_RECENT_LOCK_PKG field of the storage file of the desktop application.

[0239] The unlocking and locking method class calls the unlocking and locking data interface class to unlock the locked application and clear the keep-alive list.

[0240] Afterwards, in one scenario, when the tablet computer is in the free screen mode, in response to the user's operation of exiting the free screen mode, the tablet computer exits the free screen mode. Exemplarily, the application keeping alive method provided in the embodiment of the present application may also include:

[0241] S2221. The bottom task bar receives an operation event for exiting the free screen mode.

[0242] For example, when the desktop interface in free screen mode is displayed, the display screen receives a user click operation on the mode switching shortcut icon in the navigation bar of the desktop interface, and accordingly, the bottom task bar receives an operation event to exit the free screen mode.

[0243] S2222. The bottom task bar calls the system UI proxy class to exit the free screen mode.

[0244] S2223. The system UI proxy class calls the desktop task control class to exit the free screen mode.

[0245] S2224. The desktop task control class calls the desktop visibility control class to notify the desktop application that it has exited the free screen mode.

[0246] S2225. The desktop visibility control class calls the unlock method class and sends a mode change indication message.

[0247] In one implementation, the mode change indication information is a second value, indicating exiting the free screen mode.

[0248] S2226, the lock / unlock method class obtains the backup list from the storage file of the desktop application, calls the lock / unlock data interface class to lock the application included in the backup list, and calls the lock / unlock data interface class to save the application information of the locked application to the database of the system interface application. The lock / unlock method class clears the backup list in the storage file of the desktop application.

[0249] The lock / unlock method class determines to exit the free screen mode according to the mode change indication information. In one implementation, the lock / unlock method class obtains the backup list from the DESKTOP_RECENT_LOCK_PKG field in the storage file of the desktop application.

[0250] The locking and unlocking method class calls the locking and unlocking data interface class to lock the applications included in the backup list.

[0251] The locking and unlocking method class calls the locking and unlocking data interface class to save the application information of the locked application into the keep-alive list in the database of the system interface application.

[0252] The encryption and unlocking method class clears the backup list. In one implementation, the encryption and unlocking method class clears the DESKTOP_RECENT_LOCK_PKG field in the storage file of the desktop application.

[0253] In another scenario, when the tablet computer is in free screen mode, the tablet computer restarts to restart the system, or the tablet computer system restarts. After the system restarts, the tablet computer enters non-free screen mode. In another scenario, when the tablet computer is in free screen mode, the desktop process restarts; after the desktop process restarts, the tablet computer enters free screen mode.

[0254] Exemplarily, the application keep-alive method provided in the embodiment of the present application may also include:

[0255] S2231. The desktop main process class receives a desktop interface creation event.

[0256] After the system is restarted or the desktop process is restarted, the desktop main process class receives the event of creating a desktop interface.

[0257] S2232. The desktop main process class calls the desktop visibility control class to indicate that the mode has changed.

[0258] S2233, the desktop visibility control class calls the desktop task control class to obtain the current mode. If the current mode is not the free screen mode, execute S2234-S2235; if the current mode is the free screen mode, the mode has not changed, and exit.

[0259] In one implementation, after the system is restarted, the tablet computer enters the non-free screen mode, that is, the current mode is the non-free screen mode. After the desktop process is restarted, the tablet computer enters the free screen mode, that is, the current mode is the free screen mode.

[0260] S2234. The desktop visibility control class calls the unlock method class and sends a mode change indication message.

[0261] In one implementation, the mode change indication information is a third value, indicating that the system is restarted.

[0262] S2235, the lock / unlock method class obtains the backup list from the storage file of the desktop application, calls the lock / unlock data interface class to lock the application included in the backup list, and calls the lock / unlock data interface class to save the application information of the locked application to the database of the system interface application. The lock / unlock method class clears the backup list in the storage file of the desktop application.

[0263] In the application keeping alive method provided in the embodiment of the present application, when the mode changes, the processing logic includes:

[0264]

[0265]

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

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

[0268] In one example, see Fig.23 , which shows a possible structural diagram of the electronic device involved in the above embodiment. The electronic device 3000 includes: a processing unit 3010, a storage unit 3020 and a display unit 3030.

[0269] The processing unit 3010 is used to control and manage the actions of the electronic device 3000. The storage unit 3020 is used to store the program code and data of the electronic device 3000. The processing unit 3010 calls the program code stored in the storage unit 3020 to execute each step in the above method embodiment. The display unit 3030 is used to display the user interface of the electronic device 3000; for example, a multi-task management interface, a desktop interface, etc.

[0270] Of course, the unit modules in the electronic device 3000 include but are not limited to the processing unit 3010, the storage unit 3020 and the display unit 3030. For example, the electronic device 3000 may also include a communication unit, a power supply unit, etc. The communication unit is used for the electronic device 3000 to communicate with other electronic devices; the power supply unit is used to supply power to the electronic device 3000.

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

[0272] For example, the processing unit 3010 is a processor (such as Figure 1 The processor 110 shown in FIG. 10A ) and the storage unit 3020 may be a memory (such as Figure 1 The internal memory 130 shown in FIG. 10 ) and the display unit 3030 may be a display screen (such as Figure 1 The electronic device 3000 provided in the embodiment of the present application may be Figure 1 The electronic device 100 shown in FIG. 1 is a schematic diagram of an electronic device 100. The processor, memory, display screen, etc. may be connected together, for example, via a bus. The processor calls the program code stored in the memory to execute each step in the above method embodiment.

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

[0274] An embodiment of the present application also provides a computer-readable storage medium, which includes computer instructions. When the computer instructions are executed on the above-mentioned electronic device, the electronic device executes each function or step executed by the tablet computer in the above-mentioned method embodiment.

[0275] The embodiment of the present application further provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute each function or step executed by the tablet computer in the above method embodiment.

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

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

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

[0279] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

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

[0281] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application shall be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. An application keeping alive method, characterized in that: Applied to an electronic device, the electronic device includes a first mode and a second mode, and the method includes: In the first mode, a first multitasking management interface is displayed, wherein the first multitasking management interface includes a first card corresponding to a first application and a second card corresponding to a second application; In response to a lock operation on the first application, displaying a second multitasking management interface, the second multitasking management interface including the first card, the second card, and a lock mark corresponding to the first application; After receiving a clear recent task operation from the user on the second multi-task management interface, the second card is cleared from the second multi-task management interface; In response to a first operation by the user, displaying a desktop interface of a second mode; In response to a second operation of the user, displaying a third multitasking management interface, wherein the third multitasking management interface includes a third card corresponding to the first application; After receiving a clear recent task operation from the user on the third multi-task management interface, the third card is cleared from the third multi-task management interface; In response to a third operation by the user, displaying the desktop interface of the first mode; In response to a fourth operation of the user, a fourth multi-tasking management interface is displayed, and the fourth multi-tasking management interface does not include a card of the first application.

2. The method according to claim 1, characterized in that The method further comprises: In the first mode, displaying a fifth multitasking management interface, wherein the fifth multitasking management interface includes a fourth card corresponding to the first application and a fifth card corresponding to the second application; In response to the locking operation on the first application, displaying a sixth multi-tasking management interface, the sixth multi-tasking management interface including the fourth card, the fifth card, and a lock mark corresponding to the first application; After receiving a clear recent task operation from the user on the sixth multi-task management interface, the fifth card is cleared from the sixth multi-task management interface; In response to a fifth operation of the user, displaying a desktop interface of the second mode; In response to a sixth operation of the user, displaying a seventh multitasking management interface, wherein the seventh multitasking management interface includes a sixth card corresponding to the first application; In response to a seventh operation of the user, displaying a desktop interface of the first mode; In response to an eighth operation of the user, an eighth multi-tasking management interface is displayed, where the eighth multi-tasking management interface includes the seventh card of the first application and a lock mark corresponding to the first application.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: In the first mode, a ninth multitasking management interface is displayed, wherein the ninth multitasking management interface includes an eighth card corresponding to the first application and a ninth card corresponding to the second application; In response to the locking operation on the first application, displaying a tenth multi-task management interface, the tenth multi-task management interface including the eighth card and the ninth card and a lock mark corresponding to the first application; After receiving a clear recent task operation from the user on the tenth multi-task management interface, the ninth card is cleared from the tenth multi-task management interface; In response to a ninth operation of the user, displaying a desktop interface of a second mode; In response to a tenth operation of the user, displaying an eleventh multi-task management interface, the eleventh multi-task management interface including a tenth card corresponding to the first application; In the second mode, the electronic device restarts; After the electronic device is restarted, the desktop interface of the first mode is displayed; In response to an eleventh operation by the user, a twelfth multi-task management interface is displayed, where the twelfth multi-task management interface includes an eleventh card corresponding to the first application and a lock mark corresponding to the first application.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: In the second mode, in response to a twelfth operation of the user, a first interface is displayed, wherein the first interface includes floating windows of a plurality of applications; In response to a thirteenth operation of the user, a thirteenth multitasking management interface is displayed, the thirteenth multitasking management interface includes a twelfth card, and the twelfth card includes thumbnails of floating windows of the multiple applications.

5. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: In the second mode, a second interface is displayed, and a task bar at the bottom of the second interface includes a first application icon; In response to an operation in which the user drags the first application icon to a first position on the display screen and releases the icon, a floating window of the application indicated by the first application icon is displayed at the first position.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: In the second mode, a third interface is displayed, wherein the third interface includes a first icon; After receiving an operation of selecting the first icon by the user, multiple applications are started; and the floating windows of the multiple applications are displayed according to the layout indicated by the first icon.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: In the second mode, a fourth interface is displayed, the fourth interface includes floating windows of multiple applications displayed according to the first layout, the fourth interface also includes a second icon, and the second icon indicates the second layout; After receiving an operation of selecting the second icon by the user, the floating windows of the multiple applications are displayed according to the second layout.

8. An electronic device, characterized in that: It includes a memory, a processor and a display screen; the display screen is used to display a user interface, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, and the processor calls the computer instructions to enable the electronic device to execute the method as described in any one of claims 1-7.

9. A computer-readable storage medium having a computer program / instruction stored thereon, characterized in that: When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images