A keep-alive method and electronic device

Abstract

The application provides an application keep-alive method and an electronic device, and relates to the technical field of terminals. When the electronic device is in a non-free screen mode, an application is locked in response to a user operation. After being locked, the application cannot be removed from a multitask management interface. Then, the electronic device enters a free screen mode, and the locked application is automatically unlocked by the electronic device. After being unlocked, the application can be removed from the multitask management interface. Then, the electronic device exits the free screen mode, and the multitask management interface does not have information about the application because the application has been removed. After 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, thereby avoiding the problem that, in the free screen mode, the locking rules of a group of applications and a single application are inconsistent because a group of applications cannot be locked.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of terminal, and particularly relates to an application keep-alive method and an electronic device. BACKGROUND

[0002] After the application is started on the electronic device, the application can be closed by the user or can be killed by the system according to the process management strategy of the system.

[0003] Generally, the electronic device such as a tablet computer has various application keep-alive strategies. For example, some applications are marked so that the probability of being killed by the system is reduced. For example, for a specific application, periodic wake-up is performed so that the specific application is not killed by the system.

[0004] In an implementation manner, a locking operation can be performed on the application, and in some scenarios, the application that has been locked will not be killed by the system, thereby realizing the keep-alive of the application.

[0005] How to keep the application alive and facilitate the user to manage the application is a problem to be solved. SUMMARY

[0006] Embodiments of the present application provide an application keep-alive method and an electronic device, which can realize the keep-alive of the application in various scenarios and facilitate the user to manage the application.

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

[0008] In a first aspect, a method for maintaining the activity of an application is provided. The method includes: 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 a first application and a second card corresponding to a second application; in response to a locking operation on the first application, displaying a second multi-task management interface, the second multi-task management interface including the first card and a locking identifier corresponding to the first application, and also including the second card; after receiving a user's clear recent task operation 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 locking identifier corresponding to the first application are not cleared. In response to a first operation of the user, a desktop interface of a second mode is displayed; that is, the electronic device enters the second mode. In response to a second operation of the user, a third multi-task management interface is displayed, the third multi-task management interface including a third card corresponding to the first application and not including the locking identifier corresponding to the first application. After receiving a user's clear recent task operation 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 of the user, a desktop interface of the first mode is displayed; 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-task management interface is displayed, the fourth multi-task management interface not including a card of the first application.

[0009] In the method, in a non-free screen mode (first mode), after the user locks the application in response to an operation, the electronic device enters a 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. After that, the electronic device exits the free screen mode, and since the application has been cleared, the multi-task management interface does not have information of 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 that the locking rules of a group of applications and a single application are inconsistent due to the inability to lock a group of applications in the free screen mode.

[0010] With reference to the first aspect, in a possible implementation manner, the method further includes: when the first mode is in effect, displaying a fifth multitask management interface, the fifth multitask management interface including 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 multitask management interface, the sixth multitask management interface including the fourth card and the fifth card and a locking identifier corresponding to the first application; after receiving a user's emptying-recent-task operation on the sixth multitask management interface, the fifth card is removed from the sixth multitask management interface, and the fourth card and the locking identifier corresponding to the first application are not removed. In response to a fifth operation of the user, a desktop interface of the second mode is displayed; that is, the second mode is entered. In response to a sixth operation of the user, a seventh multitask management interface is displayed, the seventh multitask management interface including a sixth card corresponding to the first application and not including the locking identifier corresponding to the first application. In response to a seventh operation of the user, a desktop interface of the first mode is displayed; that is, the second mode is exited and the first mode is entered. In response to an eighth operation of the user, an eighth multitask management interface is displayed, the eighth multitask management interface including a seventh card of the first application and the locking identifier corresponding to the first application.

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

[0012] With reference to the first aspect, in a possible implementation manner, the method further includes: when the first mode is in effect, displaying a ninth multitask management interface, the ninth multitask management interface including 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 multitask management interface, the tenth multitask management interface including the eighth card and the ninth card and a locking identifier corresponding to the first application; after receiving a user's emptying-recent-task operation on the tenth multitask management interface, the ninth card is removed from the tenth multitask management interface, and the eighth card and the locking identifier corresponding to the first application are not removed. In response to a ninth operation of the user, a desktop interface of the second mode is displayed; that is, the second mode is entered. In response to a tenth operation of the user, an eleventh multitask management interface is displayed, the eleventh multitask management interface including a tenth card corresponding to the first application and not including the locking identifier corresponding to the first application. When the second mode is in effect, the electronic device is restarted; after the electronic device is restarted, a desktop interface of the first mode is displayed; that is, the first mode is entered. In response to an eleventh operation of the user, a twelfth multitask management interface is displayed, the twelfth multitask management interface including an eleventh card corresponding to the first application and the locking identifier corresponding to the first application.

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

[0014] With reference to the first aspect, in a possible implementation, the method further includes: in the second mode, displaying a first interface in response to a twelfth operation of the user, the first interface including the floating windows of the plurality of applications; and displaying a thirteenth multi-task management interface in response to a thirteenth operation of the user, the thirteenth multi-task management interface including a twelfth card, the twelfth card including the thumbnails of the floating windows of the plurality of applications.

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

[0016] With reference to the first aspect, in a possible implementation, the method further includes: in the second mode, displaying a second interface, the bottom task bar of the second interface including a first application icon; and displaying a floating window of an application indicated by the first application icon at a first position on the display screen in response to an operation of the user dragging the first application icon to the first position and releasing the first application icon.

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

[0018] With reference to the first aspect, in a possible implementation, the method further includes: in the second mode, displaying a third interface, the third interface including a first icon; starting a plurality of applications in response to an operation of the user selecting the first icon; and displaying the floating windows of the plurality of applications according to a layout indicated by the first icon.

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

[0020] With reference to the first aspect, in a possible implementation, the method further includes: in the second mode, displaying a fourth interface, the fourth interface including the floating windows of the plurality of applications displayed according to a first layout, the fourth interface further including a second icon, the second icon indicating a second layout; and displaying the floating windows of the plurality of applications according to the second layout in response to an operation of the user selecting the second icon.

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

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

[0023] In a third aspect, an electronic device is provided, which includes a processor, a memory and a display screen. The display screen is configured to display a user interface, and the memory is configured to store computer-executable instructions. When the electronic device is running, the processor executes the computer-executable instructions stored in the memory, so that the electronic device performs the method according to any possible implementation manner of the first aspect.

[0024] In a fourth aspect, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed on a computer, the computer can perform the method according to any possible implementation manner of the first aspect.

[0025] In a fifth aspect, a computer program product is provided, which includes instructions. When the instructions are executed on a computer, the computer can perform the method according to any possible implementation manner of the first aspect.

[0026] The technical effects brought by any possible implementation manner of the second aspect to the fifth aspect can refer to the technical effects brought by different implementation manners of the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

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

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

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

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

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

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

[0033] Figure 7A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0034] Figure 8 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0035] Figure 9 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0036] Figure 10 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0037] Figure 11 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0038] Figure 12 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0039] Figure 13 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0040] Figure 14 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0041] Figure 15 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0042] Figure 16 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0043] Figure 17 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0044] Figure 18 A scenario instance schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0045] Figure 19 A flow schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0046] Figure 20 A software structure schematic diagram of an electronic device provided by the embodiment of the present application;

[0047] Figure 21 A module interaction timing schematic diagram of the application keep-alive method provided by the embodiment of the present application;

[0048] Figure 22A module interaction timing diagram of the application provided in the embodiment;

[0049] Figure 23 A structural composition diagram of an electronic device provided in the embodiment of the 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 the specific embodiments and are not intended to be limiting of the present application. As used in the specification and the appended claims of the application, the singular forms“a,”“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms“comprises,”“comprising,”“includes” and / or“including,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. The term“and / or” used in the context of the application refers to three relationships: A and / or B, A or B, and A and B.

[0051] In this specification, the reference to“one embodiment” or“some embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the application. The appearances of the phrases“in one embodiment,”“in some embodiments,”“in other embodiments,”“in additional embodiments,” and so on, in various places in the specification are not necessarily all referring to the same embodiment, unless otherwise specifically stated. The terms“comprise,”“comprising,”“have,”“having,”“include,”“including,” and“contains,”“containing,” or variants thereof, mean“including but not limited to,” unless otherwise specified. The term“connected” includes both direct and indirect connections unless otherwise specified. The terms“first,”“second,” and“third,” etc., are used only to describe different instances, and cannot be construed as indicating or implying relative importance or an indicated number of technical features.

[0052] In the embodiments of the present application, the words“exemplary” and“for example” are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as“exemplary” or“for example” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words“exemplary” and“for example” is intended to present concepts in a concrete manner. In the embodiments of the present application, the terms“first,”“second,” and“third,” etc., are used to describe various objects, and are not necessarily used to indicate or imply relative importance or an indicated number of technical features.

[0053] The application preserving method provided by the embodiments of the present application can be applied to an electronic device including a display screen. The electronic device can include a tablet computer, a notebook computer, a personal computer (PC), a mobile phone, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a smart home device (for example, a smart television, a smart screen, a large screen, a smart speaker, a smart air conditioner, etc.), a personal digital assistant (PDA), a wearable device (for example, a smart watch, a smart bracelet, etc.), a vehicle-mounted device, a virtual reality device, and the like, and the embodiments of the present application do not make any limitation on this.

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

[0055] It can be understood that the structure illustrated in the embodiments 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 can include more or fewer components than the illustration, or combine certain components, or split certain components, or different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

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

[0057] The controller is the nerve center and command center of the electronic device 100. According to the instruction operation code and timing signal, the operation control signal can be generated to complete the control of fetching and executing instructions.

[0058] The application processor can run an operating system of the electronic device 100 for managing hardware and software resources of the electronic device 100. For example, managing and configuring memory, determining priorities of system resource supply and demand, controlling input and output devices, operating a network, managing a file system, managing a driver, and the like. The operating system can also be used to provide an operation interface for a user to interact with the system. In the operating system, various software such as a driver, an application (App), and the like can be installed.

[0059] The processor 110 can further include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that have just been used or are repeatedly used by the processor 110. If the processor 110 needs to use the instructions or data again, the instructions or data can be directly called from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thereby improving the efficiency of the system.

[0060] In some embodiments, the processor 110 can include one or more interfaces. The interfaces can 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, and the like.

[0061] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation of the electronic device 100. In some other embodiments of the present application, the electronic device 100 can also use different interface connection methods or a combination of multiple interface connection methods in the above embodiments.

[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 realize data storage functions. For example, music, video, and the like files are saved in the external memory card.

[0063] The internal memory 130 can be used to store one or more computer programs including instructions. The processor 110 can cause the electronic device 100 to perform the methods provided by some embodiments of the present application, as well as various applications and data management, etc., by running the above-mentioned instructions stored in the internal memory 130. The internal memory 130 can include a code storage area and a data storage area. The data storage area can store data created during the use of the electronic device 100, etc. In addition, the internal memory 130 can include a high-speed random access memory, and can further include a non-volatile memory such as one or more disk storage components, flash memory components, universal flash storage (UFS), etc. In some embodiments, the processor 110 can cause the electronic device 100 to perform the methods provided by 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 disposed in the processor 110.

[0064] The electronic device 100 implements a display function through a GPU, a display screen 140, and an application processor, etc. The GPU is a microprocessor for image processing, connected to the display screen 140 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 can include one or more GPUs that 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 adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-oLed, a quantum dot light emitting diode (QLED), etc. In some embodiments, the electronic device 100 can include 1 or N display screens 140, N being a positive integer greater than 1.

[0066] In some embodiments, the display screen 140 is provided with a pressure sensor, a touch sensor, etc. The pressure sensor is used to sense a pressure signal, which can be converted into an electrical signal. When a touch operation is applied to the display screen 140, the electronic device 100 detects the touch operation intensity according to the pressure sensor. The electronic device 100 can also calculate the touch position 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 a touch operation applied thereto or in the vicinity. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can also be provided through the display screen 140.

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

[0068] The power module 160 can be used to power the 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 describes in detail the application preservation method provided by the embodiments of the application, taking a tablet computer as an example.

[0070] Generally, a tablet computer has a multi-task management interface. The multi-task management interface can also be referred to as a multi-task interface, a background application interface, a Recent interface, etc. The multi-task management interface is used to display information of applications recently started on the tablet computer, such as application icons, application names, thumbnails, etc.

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

[0072] In one example, applications C, B, and A were launched on tablet 100 in the order they were started. In response to an operation to open the multitasking management interface, tablet 100 displays the multitasking management interface 201. For example, as shown... Figure 2 As shown in (a), the multitasking management interface 201 includes an icon 2011, an application name 2012, and a card 2013 for application A. For example, card 2013 includes a thumbnail of the full-screen window of application A. The multitasking management interface 201 also includes an icon 2014, an application name 2015, and a card 2016 for application B. For example, card 2016 includes a thumbnail of the full-screen window of application B. The multitasking management interface 201 also includes an icon 2017, an application name 2018, and a card 2019 for application C. For example, card 2019 includes a thumbnail of the full-screen window of application C. In this embodiment, 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] Users can open the user interface of any application in the multitasking management interface, and the corresponding application will run in the foreground. For example, in response to the user clicking on the thumbnail of application B's window in the multitasking management interface 201, the electronic device displays the user interface of application B, that is, application B runs in the foreground.

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

[0075] Users can also clear the multitasking management interface, specifically clearing the most recent tasks (most recently opened applications) from the interface. In one implementation, in response to a user's action to clear the multitasking management interface, the most recent tasks are cleared. For example, the multitasking management interface includes a "Clear" control; receiving a user's click on the "Clear" control signifies receiving the action to clear the multitasking management interface. For instance, as shown... Figure 2 As shown in (a), the multitasking management interface 201 also includes a "clear" control 202. Users 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, as... Figure 2As shown in (b), in response to the user's click on the "Clear" control 202, the tablet computer 100 displays a multitasking management interface 203; the multitasking management interface 203 does not contain any information (icons, names, cards) related to application A, application B, and application C. When the application information is cleared from the multitasking management interface, the application is killed by the system if it is running in the background.

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

[0077] If an application is locked, when a message is received to clear the multitasking management interface, the locked application will not be removed from the multitasking management interface; instead, all applications in the multitasking management interface will be cleared. Correspondingly, the locked application will not be killed. In other words, locking an application effectively keeps it alive.

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

[0079] For example, such as Figure 3 As shown in (c), in response to the user's click on the "Clear" control 202, the tablet computer 100 displays a multitasking management interface 204. The multitasking management interface 204 does not contain any information (icons, names, cards) related to applications B and C. The multitasking management interface 204 includes an icon 2011 for application A, an application name 2012, a card 2013, and a "lock" icon 2020. In other words, after receiving the user's operation to clear the multitasking management interface, application A is not cleared, but applications other than application A (applications B and C) are cleared from the multitasking management interface.

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

[0081] Once a locked application is unlocked, it will be deleted when the multitasking management interface is cleared.

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

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

[0084] In some embodiments, the tablet computer includes special modes, such as a free screen mode. Free screen mode can also be called a multi-tasking mode, desktop mode, etc. In this embodiment, the state not in free screen mode or after exiting free screen mode is called a non-free screen mode. A non-free screen mode can be another special mode, or it may not be any special mode. In one example, non-free screen mode can be called a first mode, and free screen mode can be called a second mode.

[0085] The following is an introduction to the free screen mode.

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

[0087] The desktop interface 301 can further include one or more bottom navigation bars. For example, as shown in (a) of FIG. 3, the desktop interface 301 includes a navigation bar 302 and a navigation bar 303; the navigation bar 302 includes a plurality of application icons, the application icons in the navigation bar 302 are preset, for example, the icons of the applications frequently used by the user can be set in the navigation bar 302; the navigation bar 303 includes a plurality of application icons, the icons of the recently started applications are displayed in the navigation bar 303. Figure 5

[0088] As shown in (a) of FIG. 3, the navigation bar 302 includes a mode switching shortcut icon 304, the user can make the tablet 100 enter the free screen mode through the operation (for example, the clicking operation) on the mode switching shortcut icon 304. Figure 5

[0089] For example, as shown in (b) of FIG. 3, in response to the clicking operation of the user on the mode switching shortcut icon 304, the tablet 100 displays a 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 a plurality of application icons, the desktop interface 305 can further include some cards, for example, a weather card and the like, the desktop interface 305 can further include a folder and the like. In an example, the application icons, the cards, the folder and the like included in the desktop interface 305 are the same as those in the desktop interface 301. Figure 5

[0090] The desktop interface 305 can further include one or more bottom navigation bars. For example, as shown in (b) of FIG. 3, the desktop interface 305 includes a navigation bar 306 and a navigation bar 307; the navigation bar 306 includes a plurality of application icons, the application icons in the navigation bar 306 are preset, for example, the icons of the applications frequently used by the user can be set in the navigation bar 306; the navigation bar 307 includes a plurality of application icons, the icons of the recently started applications are displayed in the navigation bar 307. Figure 5 As shown in (b) of FIG. 3, the navigation bar 306 includes a mode switching shortcut icon 308, the user can make the tablet 100 exit the free screen mode through the operation (for example, the clicking operation) on the mode switching shortcut icon 308. For example, as shown in (a) of FIG. 3, in response to the clicking operation of the user on the mode switching shortcut icon 308, the tablet 100 displays the desktop interface 301 of the non-free screen mode.

[0091] Figure 5 Figure 5 Optionally, the navigation bar 306 further includes a “layout” icon 309, the user can set the layout of the application window in the free screen mode through the operation on the “layout” icon 309. The “layout” icon 309 will be described in detail later.

[0092] ​​​​​​

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

[0094] Taking full-screen application display as an example: If you launch application A, application B, and application C sequentially in non-free screen mode, you can launch application A first, and the tablet will display the window of application A; then launch application B, and the tablet will display the window of application B, closing the window of application A; then launch application C, and the tablet will display the window of application C, closing the window of application B.

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

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

[0097] For example, such as Figure 6 As shown, the tablet computer 100 displays a desktop interface 301 in non-free screen mode, and applications A, B, C, D, and E are running on the tablet computer 100. In response to a user opening a multitasking management interface, the tablet computer 100 displays a multitasking management interface 401. The multitasking management interface 401 includes relevant information (icons, names, cards) for applications A, B, C, D, and E. Optionally, applications D and E are displayed in a split-screen format, and correspondingly, the card size for applications D and E in the multitasking management interface 401 is half the size of that for application A (or application B or application C). In one implementation, each application in the multitasking management interface 401 corresponds to one card.

[0098] Afterwards, the tablet enters free screen mode, for example, receiving user input... Figure 6 After clicking the mode switching shortcut icon 304 on the desktop interface 301, as follows: Figure 7 As shown in (a), the tablet computer 100 displays a desktop interface 305 in free-screen mode. In response to a user opening a multitasking management interface, the tablet computer 100 displays a multitasking management interface 402, which includes information about applications A, B, C, D, and E. In one implementation, as... Figure 7As shown in (b) of FIG. 4, the multi-task management interface 402 includes card 4021, card 4022, card 4023 and card 4024, wherein card 4021 includes a thumbnail of the floating window of application A, card 4022 includes a thumbnail of the floating window of application B, card 4023 includes a thumbnail of the floating window of application C, and card 4024 includes thumbnails of the floating windows of application D and application E. That is, each card corresponds to all the applications displayed on the screen simultaneously.

[0099] In the free screen mode, the tablet computer can display floating windows of a plurality of applications on one screen, the plurality of applications being a group. In an implementation, when the tablet computer is in the free screen mode, the tablet computer displays a desktop interface, and then starts a plurality of applications through the desktop interface, wherein each window of each application is displayed in the form of a floating window, and the plurality of applications are a group. After the tablet computer exits the desktop interface, the tablet computer enters the desktop interface again, and then starts another group of applications. That is, the applications started by the tablet computer between the time when the tablet computer enters the desktop interface and the time when the tablet computer exits the desktop interface are a group of applications. 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 a user's dragging operation on the floating window. One floating window can cover a part of another window.

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

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

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

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

[0104] In some examples, as shown in (a) of FIG. 3, the tablet 100 displays a desktop interface 305 of the free screen mode, the desktop interface 305 being a main interface of the free screen mode, and a navigation bar 306 of the desktop interface 305 including a "layout" icon 309. As shown in (b) of FIG. 3, in response to the user's clicking operation on the "layout" icon 309, the tablet 100 displays a "shortcut layout" interface 320, and the "shortcut layout" interface 320 includes multiple layout templates, each of which defines a layout format of multiple windows of a group of applications. For example, the "shortcut layout" interface 320 includes a layout template 3201. Figure 9 Figure 9

[0105] In an example, as shown in (a) of FIG. 3, in response to the user's clicking operation on the layout template 3201, the tablet displays a user interface 330, and the user interface 330 includes a region 1, a region 2 and a region 3, and the layout formats of the region 1, the region 2 and the region 3 are the same as the layout format indicated by the layout template 3201. Figure 10

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

[0107] ​​​​In one implementation, a user can launch application F by clicking icon 3301, application G by clicking icon 3302, and application H by clicking icon 3303. 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 the order in which application F, application G, and application H are launched.

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

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

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

[0111] In one implementation, such as Figure 12 As shown in (a), in response to a user's click on layout template 3501, tablet computer 100 displays user interface 360, which includes region 1, region 2, and region 3. The layout format of regions 1, 2, and 3 is the same as the layout format indicated by layout template 3501. Region 1 includes thumbnails of floating windows for applications F, G, and 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 region 1, so that the tablet 100 displays the window of application F in region 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 region 2, so that the tablet 100 displays the window of application G in region 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 region 3, so that the tablet 100 displays the window of application H in region 3. For example, Figure 12 As shown in (b) of FIG. 3, the tablet 100 displays a user interface 370 including the floating windows of application F, application G and application H, wherein the window of application F is displayed in region 1, the window of application G is displayed in region 2, and the window of application H is displayed in region 3.

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

[0114] In some other examples, as shown in (a) of FIG. 4, the tablet 100 displays a user interface 380 including region 1, region 2 and region 3. The window of application F is displayed in region 1, the window of application G is displayed in region 2, and the window of application H is displayed in region 3. Figure 13

[0115] The bottom navigation bar of the user interface 380 includes a "layout" icon 3801. In response to the user's click operation on the "layout" icon 3801, the tablet 100 displays a "shortcut layout" interface 381, and the "shortcut layout" interface 381 includes a plurality of layout templates, each of which defines a layout format of a plurality of windows of a group of applications. For example, the "shortcut layout" interface 381 includes a layout template 3811 and a layout template 3812. Wherein the layout formats of region 1, region 2 and region 3 in the user interface 380 are the same as the layout format indicated by the layout template 3811.

[0116] As shown in (b) of FIG. 4, the tablet 100 displays a user interface 390 including region 1, region 2 and region 3. The window of application F is displayed in region 1, the window of application G is displayed in region 2, and the window of application H is displayed in region 3. Figure 13 ​As shown in (b) of FIG. 38, in response to the clicking operation of the user on the layout template 3812, the tablet 100 displays a user interface 390, which includes a region 4, a region 5 and a region 6, and the layout format of the region 4, the region 5 and the region 6 is the same as the layout format indicated by the layout template 3812. The window of the application F is displayed in the region 4, the window of the application G is displayed in the region 5, and the window of the application H is displayed in the region 6.

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

[0118] In some embodiments, in the non-free screen mode, the tablet can lock or unlock one application in the multi-task management interface. When the tablet enters the free screen mode from the non-free screen mode, if there is an application that has been locked, since the tablet cannot lock or unlock a group of applications, the locking and unlocking rules of the single application and the group of applications will be inconsistent. In the embodiments of the present application, when the tablet enters the free screen mode from the non-free screen mode, the tablet uniformly unlocks all the applications that have been locked. In this way, the confusion caused by the fact that in the free screen mode, the single application can be locked, but the group of applications cannot be locked, and thus some applications can be locked and some applications cannot be locked, can be avoided.

[0119] In an example, in the non-free screen mode, the applications C, B and A are started on the tablet 100 in sequence. As an example, as shown in (a) of FIG. 50, in response to the operation of the user opening the multi-task management interface, the tablet 100 displays a multi-task management interface 501, which includes an icon 5011 of the application A, an application name 5012, and a card 5013, for example, the card 5013 includes a thumbnail of the full-screen window of the application A; the multi-task management interface 501 further includes an icon 5014 of the application B, an application name 5015, and a card 5016, for example, the card 5016 includes a thumbnail of the full-screen window of the application B; the multi-task management interface 501 further includes an icon 5017 of the application C, an application name 5018, and a card 5019, for example, the card 5019 includes a thumbnail of the full-screen window of the application C. In the multi-task management interface 501, the "lock" icon 502 is displayed beside the application name 5012 of the application A and above the card 5013. The "lock" icon 502 indicates that the corresponding application (application A) has been locked. As an example, the multi-task management interface 501 can be the multi-task management interface 201 in (b) of FIG. 2. Figure 14 Figure 14 The multi-task management interface 501 in (a) of FIG. 50 can be the multi-task management interface 201 in (b) of FIG. 2. Figure 3 The multi-task management interface 201 in (b) of FIG. 2.

[0120] ​After application A has been locked, when receiving an operation of a user clearing the multi-task management interface, application A will not be cleared. Exemplarily, refer to Figure 3 .

[0121] In some examples, when application A, application B and application C are running on the tablet 100, the tablet 100 enters the free screen mode. Exemplarily, as shown in (b) of Figure 14 , the tablet 100 displays a desktop interface 503 in the 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. Exemplarily, as shown in (c) of Figure 14 , in response to a click operation of the user on the mode switching shortcut icon 5041, the tablet 100 displays a desktop interface 505 in 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 an operation of the user opening the multi-task management interface, as shown in (d) of Figure 14 , the tablet 100 displays a multi-task management interface 507, and the multi-task management interface 507 includes an icon 5071 of application A, an application name 5072, and a card 5073 including a thumbnail of a floating window of application A; the multi-task management interface 507 further includes an icon 5074 of application B, an application name 5075, and a card 5076 including a thumbnail of a floating window of application B; the multi-task management interface 507 further includes an icon 5077 of application C, an application name 5078, and a card 5079 including a thumbnail of a floating window of application C. Wherein, application A has been unlocked, and the multi-task 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 receiving an operation of the user clearing the multi-task management interface, application A will be cleared. Exemplarily, as shown in (a) of Figure 15 , the multi-task management interface 507 further includes a “clear” control 508. The user can click the “clear” control 508 to kill application A, application B and application C. Exemplarily, as shown in (b) of Figure 15 , in response to a click operation of the user on the “clear” control 508, the tablet 100 displays a multi-task management interface 509; and the multi-task management interface 509 does not include related information (icon, name, card) of application A, application B and application C.

[0124] After that, the tablet 100 exits the free screen mode. Exemplarily, as shown in (c) of Figure 15 .As shown in (c), the tablet 100 displays a desktop interface 510 of the free screen mode, which includes a navigation bar 520 including a mode switching shortcut icon 5201 and a "layout" icon 5202, etc. As an example, as shown in (c), the desktop interface 510 includes a "layout" icon 5202, which is used to switch the layout of the desktop interface 510. Figure 15 As shown in (d), in response to a click operation of the user on the mode switching shortcut icon 5201, the tablet 100 displays a desktop interface 530 of the non-free screen mode.

[0125] In the non-free screen mode, in response to an operation of the user to open a multi-task management interface, as shown in (e), the tablet 100 displays a multi-task management interface 540, which does not include the related information (icon, name, card, etc.) of the applications A, B and C. Figure 15

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

[0127] In some embodiments, after the tablet 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. After that, when the tablet exits the free screen mode and enters the non-free screen mode, the locked applications are locked according to the saved information. In this way, the state of the locked applications can be avoided from being lost after the mode switching of the tablet.

[0128] In an example, as shown in (a), in the non-free screen mode, the tablet 100 starts the application A first, and then starts the application B and the application C. In response to an operation of the user to open a multi-task management interface, the tablet 100 displays a multi-task management interface 501, which includes the related information (icon, name, card, etc.) of the applications A, B and C. The multi-task management interface 501 further includes a "lock" icon 502 corresponding to the application A, i.e., the application A has been locked. Figure 14 In the example shown in (a), in the non-free screen mode, the tablet 100 starts the application C first, and then starts the application B and the application A. In response to an operation of the user to open a multi-task management interface, the tablet 100 displays a multi-task management interface 501, which includes the related information (icon, name, card, etc.) of the applications A, B and C. The multi-task management interface 501 further includes a "lock" icon 502 corresponding to the application A, i.e., the application A has been locked. Figure 14 ​As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes relevant information (icons, names, cards, etc.) for application A, application B, and application C. The multitasking management interface 507 does not include the "lock" icon corresponding to application A.

[0129] Afterwards, tablet computer 100 exits free screen mode. For example, as shown... Figure 16 As shown in (a), the tablet computer 100 displays a desktop interface 550 in free-screen mode. The desktop interface 550 includes a navigation bar 560, which includes a mode switching shortcut icon 5601 and a "layout" icon 5602, etc. For example, as... Figure 16 As shown in (b), in response to the user's click on the mode switching shortcut icon 5601, the tablet computer 100 displays the desktop interface 570 in non-free screen mode.

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

[0131] In another example, such as Figure 14 In the example shown, in non-free screen mode, application C, application B, and application A were launched sequentially on tablet computer 100. In response to the user opening the multitasking management interface, tablet computer 100 displays multitasking management interface 501. Multitasking management interface 501 includes relevant information (icons, names, cards, etc.) for applications A, B, and C. Multitasking management interface 501 also includes a "lock" icon 502 for application A, indicating that application A is locked. Afterwards, tablet computer 100 enters free screen mode. In free screen mode, in response to the user opening the multitasking management interface, as shown... Figure 14As shown in (d), the tablet computer 100 displays a multitasking management interface 507, which includes relevant information (icons, names, cards, etc.) for application A, application B, and application C. The multitasking management interface 507 does not include the "lock" icon corresponding to application A.

[0132] After that, as Figure 17 As shown in (a), when the tablet computer 100 displays the multitasking management interface 507, after receiving a 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. Figure 17 As shown in (b), in response to a click on a thumbnail of the floating window of application A in card 5073, tablet computer 100 displays user interface 601, which includes the floating window 602 of application A. Optionally, user interface 601 includes a navigation bar 603, which includes application icons 6031. Figure 17 As shown in (c), in response to a user pressing and dragging an application icon 6031 and releasing it at a location on the screen, the tablet computer 100 displays a user interface 604, which includes a floating window 602 for application A and a floating window 605 for application F. Optionally, the floating window 605 of application F is displayed at the location where the user pressed and dragged the application icon 6031 and released it on the screen.

[0133] After that, as Figure 17 As shown in (d), in response to the user's operation of opening the multitasking management interface, the tablet computer 100 displays the multitasking management interface 606. The multitasking management interface 606 includes an icon 6061 for application A, an icon 6062 for application F, a name 6063 for application A, a name 6064 for application F, and a card 6065. Card 6065 includes thumbnails of the floating windows of applications A and F. The multitasking management interface 606 also includes an icon 6066 for application B, a name 6067 for application B, and a card 6068 (including a thumbnail of the floating window of application B). The multitasking management interface 606 also includes an icon 6069 for application C, a name 606a for application C, and a card 606b (including a thumbnail of the floating window of application C). The inclusion of thumbnails of the floating windows of applications A and F in card 6065 indicates that applications A and F are a group of applications. The multitasking management interface 606 does not include a "lock" icon for application A, indicating that application A has been unlocked.

[0134] Afterwards, the tablet 100 exits free screen mode. For example, the tablet 100 can exit free screen mode and enter non-free screen mode by clicking the mode switching shortcut icon; this process will not be detailed here. In non-free screen mode, in response to the user's operation of opening the multitasking management interface, such as... Figure 17As shown in (e) of FIG. 6, the tablet 100 displays a multitask management interface 607, which includes an icon 6071, a name 6072, a card 6073 (including a thumbnail of a full-screen window of the application A) of the application A, an icon 6074, a name 6075, a card 6076 (including a thumbnail of a full-screen window of the application B) of the application B, an icon 6077, a name 6078, a card 6079 (including a thumbnail of a full-screen window of the application C) of the application C, an icon 6081, a name 6082, a card 6083 (including a thumbnail of a full-screen window of the application F) of the application F. Among them, a "lock" icon 609 is displayed beside the name 6072 of the application A and above the card 6073, indicating that the 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.

[0135] In this embodiment, in the non-free screen mode, after the application is locked in response to the user operation, the tablet enters the free screen mode, and the locked application is automatically unlocked by the tablet. Then, the tablet exits the free screen mode, and the application is automatically locked by the tablet. In this way, when the tablet locks the application in response to the user operation, even if the mode changes, 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 restarts or the system restarts, etc. in the free screen mode, after the restart, the tablet enters the non-free screen mode, and the tablet automatically locks the applications that have been locked before entering the free screen mode (these applications have been unlocked after entering the free screen mode).

[0137] For example, referring to Figure 14 In the non-free screen mode, the applications C, B and A are started on the tablet 100 in sequence. In response to the user's operation of opening the multitask management interface, the tablet 100 displays a multitask management interface 501, which includes the relevant information (icon, name, card, etc.) of the applications A, B and C, and further includes a "lock" icon 502 corresponding to the application A, indicating that the application A has been locked. Then, the tablet 100 enters the free screen mode, and in the free screen mode, in response to the user's operation of opening the multitask management interface, as shown in (d) of FIG. 5, the tablet 100 displays a multitask management interface 507, which includes the relevant information (icon, name, card, etc.) of the applications A, B and C, and does not include the "lock" icon corresponding to the application A. Figure 14

[0138] ​If the tablet 100 is restarted or the system of the tablet 100 is restarted, the tablet 100 is in the non-free screen mode after the restart, and the application A is locked by the tablet 100. Exemplarily, as shown in (a) of FIG. 7, the tablet 100 displays the multitask management interface 507. Then, as shown in (b) of FIG. 7, the tablet 100 is restarted, and after the restart, the tablet 100 displays the desktop interface 701 in the non-free screen mode. Then, as shown in (c) of FIG. 7, in response to the operation of the user opening the multitask management interface, the tablet 100 displays the multitask management interface 501, and the multitask management interface 501 includes the "lock" icon 502 corresponding to the application A. Figure 18 Figure 18 Figure 18

[0139] Exemplarily, as shown in (a) of FIG. 8, the application keep-alive method provided by the embodiment of the present application can include the following steps. Figure 19

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

[0141] Exemplarily, in the non-free screen mode, the user can perform a lock operation on any one of the applications in the multitask management interface. The tablet locks the application in response to the lock operation of the user in the multitask management interface. For example, as shown in (a) of FIG. 6, the user performs a lock operation on the application A in the multitask management interface 201. As shown in (b) of FIG. 6, the "lock" icon 2020 is displayed above the card 2013 of the application A. Figure 3 Figure 3

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

[0143] When the applications are cleared in the multitask management interface, the applications included in the keep-alive list are not cleared.

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

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

[0146] ​​​​​​​S803, the tablet computer enters the non-free screen mode, locks the applications included in the backup list, writes the application information of the locked applications into the 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. For example, as shown in (c) of FIG. 5, the tablet computer 100 displays the desktop interface 510 of the free screen mode, and the desktop interface 510 includes the mode switching shortcut icon 5201. After receiving the click operation of the user on the mode switching shortcut icon 5201, the tablet computer 100 exits the free screen mode. Figure 15

[0148] In another scenario, when in the free screen mode, the tablet computer is restarted, or the system of the tablet computer is restarted. 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 computer 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 are not cleared.

[0150] In this embodiment, when the tablet computer enters the free screen mode from the non-free screen mode, all the locked applications are unlocked, so that in the free screen mode, all the applications are not locked. In addition, before the keep-alive list is cleared, the information in the keep-alive list is saved to the backup list, and the backup list can be used to lock the applications 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 application information of the locked applications is saved to the keep-alive list, so that after exiting the free screen mode, the applications are automatically locked, and the application information of the locked applications is not lost.

[0151] The application keep-alive method provided in the embodiments of the present application can be applied to an electronic device including a display screen. In the embodiments 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 an Android system, an iOS system, a Windows system, and the like.

[0152] The software system of the electronic device 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiments of the present application take the layered architecture as an example to exemplarily illustrate the software structure of the electronic device 100.

[0153] Figure 20 is a schematic diagram of one software structure of the electronic device 100.​​

[0154] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, [the following is omitted as the text is incomplete and likely refers to a specific implementation or feature]. The system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0155] The application layer can include a series of application packages. For example, desktop applications, SystemUI applications, etc.

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

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

[0158] The window management module is used to manage window applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture the screen, among other things.

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

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

[0161] The resource management module provides the application with various resources, 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 entered by the user into the electronic device 100 via a keyboard, by the user into the electronic device 100 via a touch screen, or by the user into the electronic device 100 via a sensor, etc.

[0163] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for... System scheduling and management.

[0164] The core library includes two parts: one part is the function function called by the java language, and the other part is The core library of the application framework layer.

[0165] The application layer and the application framework layer run in the virtual machine. The virtual machine executes the java file of the application layer and the application framework layer as a binary file. The virtual machine is used to execute the management of the object life cycle, the management of the stack, the management of the thread, the management of the security and the exception, and the garbage collection and the like.

[0166] The system library can include a plurality of function modules. For example: surface manager, media library, three-dimensional graphics processing library (for example: OpenGL ES), 2D graphics engine (for example: SGL) and the like.

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

[0168] The application alive method provided by the embodiment of the application will be introduced below. Figure 20 The application alive method provided by the embodiment of the application will be introduced below.

[0169] For example, as shown in Figure 21 The application alive method provided by the embodiment of the application can include:

[0170] S2101, the input management module receives the locking operation event of the application one, and sends the locking operation event to the desktop application.

[0171] The locking operation event includes the application information of the application executing the locking operation, for example, the application package name.

[0172] S2102, the desktop application locks the application one.

[0173] For example, the multi-task management interface is updated, and the updated multi-task management interface displays the "locking" icon corresponding to the application one.

[0174] S2103, the desktop application notifies the system interface application that the application one has been locked.

[0175] S2104, the system interface application writes the application information of the application one into the alive list.

[0176] In this way, when the application is emptied in the multi-task management interface, the application one will not be cleared.

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

[0178] Then, the application preserving method provided by the embodiments of the present application can further include:

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

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

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

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

[0183] S2114, the desktop application acquires the application information in the preserving list from the system interface application.

[0184] S2115, the desktop application saves all the application information in the preserving list to the backup list.

[0185] S2116, the desktop application unlocks the applications included in the preserving list, and notifies the system interface application to clear the preserving list.

[0186] After the application is unlocked, the "locked" icon corresponding to the application will not be displayed in the multitask management interface.

[0187] S2117, the system interface application clears the preserving list.

[0188] Then, in one scenario, when the tablet computer is in the free screen mode, the tablet computer exits the free screen mode in response to the operation of the user for exiting the free screen mode. For example, the application preserving method provided by the embodiments of the present application can further include:

[0189] S2121, the input management module receives an exiting free screen mode operation event, 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 computer to the non-free screen mode.

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

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

[0194] After the application is locked, the "locked" icon corresponding to the application will be included in the multitask management interface.

[0195] S2125, the desktop application notifies the system interface application to write the application information of the application that has been locked into the keep-alive list.

[0196] S2126, the system interface application writes the application information of the application that has been locked into the keep-alive list.

[0197] S2127, the desktop application clears the backup list.

[0198] In another scenario, when the tablet is in the free screen mode, the tablet restarts, the system restarts, or the system of the tablet restarts. After the system restarts, the tablet enters the non-free screen mode. Illustratively, the application keep-alive method provided by the embodiments of the present application can further include:

[0199] S2131, after the system restarts, the desktop application creates the desktop interface. When creating the desktop interface, the desktop application queries the current mode of the tablet from the system interface application. After the system restarts, the current mode of the tablet is the 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 applications included in the backup list.

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

[0203] S2133, the desktop application notifies the system interface application to write the application information of the application that has been locked into the keep-alive list.

[0204] S2134, the system interface application writes the application information of the application that has been locked into the keep-alive list.

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

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

[0207] It can be understood that the desktop application and the system interface application include a plurality of sub-modules (classes), and each class of the desktop application and each class of the system interface application perform corresponding logic when the tablet computer executes each step shown in the flowchart. Figure 21

[0208] In an example, the desktop application includes Launcher (desktop main process class), HnDesktopVisibilityController (desktop visibility control class), Hotseat switch (hotkey switch), Taskbar (bottom taskbar), SystemUIProxy (system UI proxy class), TaskViewHeader (task icon class), HnRecentsLockUtils (lock / unlock method class), etc.

[0209] The system interface application includes HwRecentsLockProvider (lock / unlock data interface class), DesktopTaskController (desktop task control class), etc.

[0210] The Launcher (desktop main process class) is the main process of the desktop application.

[0211] The 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, empty the desktop elements outside the application window; for example, entering the free screen mode to make the application window of the free screen mode visible, and exiting the free screen mode to make the application window of the non-free screen mode visible.

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

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

[0214] The SystemUIProxy (system UI proxy class) is used to manage cross-process calling interfaces, such as the system interface called by the SystemUI or indirectly called through the SystemUI.

[0215] The 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 an application in the multitasking management interface.

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

[0218] DesktopTaskController (desktop task control class) is used to control entering or exiting the free screen mode, and is also used to implement the free screen mode, for example, converting an application window into a floating window after detecting that the application opens a full-screen window or a split-screen window in the free screen mode, and managing the number of applications opened in the foreground.

[0219] As shown in FIG. 8, the application keep-alive method provided by the embodiments of the present application can include the following steps. Figure 22

[0220] S2201, the task icon class receives a lock operation event of an application 1.

[0221] In an example, after the display screen receives a user operation of pressing down and then releasing the card corresponding to the application 1 in the multitasking management interface, the display driver generates a lock operation event. After the task icon class receives the lock operation event, it is determined that the lock operation event of the application 1 is received.

[0222] S2202, the task icon class locks the application 1.

[0223] In an example, the task icon class displays a "lock" icon corresponding to the application 1 in the multitasking management interface.

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

[0225] S2204, the lock and unlock method class calls the lock and unlock data interface class to save the information of the application 1 to the database of the system interface application.

[0226] In an implementation mode, 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 an application is locked, the application information of the application that has been locked is written to 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 method for keeping alive provided by the embodiment of the present application can further include:

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

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

[0231] S2212, the hot key switch calls a system UI agent class to enter the free screen mode.

[0232] S2213, the system UI agent class calls a desktop task control class to enter the free screen mode.

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

[0234] S2215, the desktop visibility control class calls a lock and unlock method class to send mode change indication information.

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

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

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

[0238] The lock and unlock method class saves the application information of the application that has been locked in the storage file of the desktop application. For example, the storage file is a backup list. In an implementation method, the application information of the application that has been locked is saved in a DESKTOP_RECENT_LOCK_PKG field of the storage file of the desktop application.

[0239] The lock and unlock method class calls the lock and unlock data interface class to unlock the application that has been locked, and clears the keep-alive list.

[0240] Afterwards, in one scenario, when the tablet is in the free screen mode, the tablet exits the free screen mode in response to a user operation of exiting the free screen mode. For example, the application keep-alive method provided by the embodiments of the present application can further include:

[0241] S2221, the bottom task bar receives an exit free screen mode operation event.

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

[0243] S2222, the bottom task bar calls a system UI agent class to exit the free screen mode.

[0244] S2223, the system UI agent class calls a desktop task control class to exit the free screen mode.

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

[0246] S2225, the desktop visibility control class calls a lock and unlock method class to send mode change indication information.

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

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

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

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

[0251] The lock and unlock method class calls the lock and unlock data interface class to save the application information of the locked applications to a keep-alive list in the database of system interface applications.

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

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

[0254] Exemplarily, the application keeping alive method provided by the embodiment of the application can further include:

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

[0256] After the system restarts, or after the desktop process restarts, the desktop main process class receives a desktop interface creation event.

[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 the non-free screen mode, S2234-S2235 are executed; if the current mode is the free screen mode, the mode has not changed, and the process exits.

[0259] In an implementation manner, after the system restarts, the tablet enters the non-free screen mode, i.e., the current mode is the non-free screen mode. After the desktop process restarts, the tablet enters the free screen mode, i.e., the current mode is the free screen mode.

[0260] S2234, the desktop visibility control class calls the lock and unlock method class to send mode change indication information.

[0261] In an implementation manner, the mode change indication information is a third value, indicating the system restarts.

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

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

[0264]

[0265]

[0266] It can be understood that, in order to realize the above functions, the electronic device provided in the embodiments of the present application comprises the hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present application, the embodiments of the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of the present application.

[0267] The embodiments of the present application can divide the functional modules of the electronic device according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or software functional module. It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical functional division. Actual implementation can have another division manner.

[0268] In an example, refer to Figure 23 which shows a possible structural schematic diagram of the electronic device involved in the above embodiments. The electronic device 3000 comprises a processing unit 3010, a storage unit 3020 and a display unit 3030.

[0269] The processing unit 3010 is configured to control and manage the actions of the electronic device 3000. The storage unit 3020 is configured to save the program code and data of the electronic device 3000. The processing unit 3010 invokes the program code stored in the storage unit 3020 to execute each step in the above method embodiments. The display unit 3030 is configured to display the user interface of the electronic device 3000, such as a multi-task management interface, a desktop interface, etc.

[0270] Of course, the unit modules in the above electronic device 3000 include but are not limited to the above processing unit 3010, storage unit 3020 and display unit 3030. For example, the electronic device 3000 can further comprise a communication unit, a power supply unit, etc. The communication unit is configured to enable the electronic device 3000 to communicate with other electronic devices. The power supply unit is configured to supply power to the electronic device 3000.

[0271] The processing unit 3010 can be a processor or a controller, for example, 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 device, a transistor logic device, a hardware component, or any combination thereof. The storage unit 3020 can be a memory. The display unit 3030 can be a display screen or the like.

[0272] For example, the processing unit 3010 is a processor (such as the processor 110 shown in FIG. 1), the storage unit 3020 can be a memory (such as the internal memory 130 shown in FIG. 1), and the display unit 3030 can be a display screen (such as the display screen 140 shown in FIG. 1). The electronic device 3000 provided by the embodiment of the present application can be the electronic device 100 shown in FIG. 1. The above processor, memory, display screen, etc. can be connected together, for example, through a bus. The processor invokes the program code stored in the memory to execute the steps in the above method embodiments. Figure 1 Figure 1 Figure 1 Figure 1

[0273] The embodiment of the present application further provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected through a line. For example, the interface circuit can be used to receive signals from other devices (such as the memory of the electronic device). For another example, the interface circuit can be used to send signals to other devices (such as the processor). Illustratively, the interface circuit can read the 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 steps in the above embodiments. Of course, the chip system can also include other discrete devices, which are not limited in the embodiment of the present application.

[0274] The embodiment of the present application further provides a computer readable storage medium, which includes computer instructions. When the computer instructions are run on the above electronic device, the electronic device performs the functions or steps of the tablet computer in the above method embodiments.

[0275] The embodiment of the present application further provides a computer program product, which makes the computer perform the functions or steps of the tablet computer in the above method embodiments when the computer program product is run on the computer. ​​​​

[0276] Through the description of the above embodiments, those skilled in the art can clearly understand that, for the convenience and brevity of description, only the division of the above functional modules is exemplified, and in actual application, the above functions can be completed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0277] In several embodiments provided in the present application, it should be understood that the disclosed device and method 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, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another device, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

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

[0279] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit. The above integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0280] The integrated unit, if realized in the form of a software functional unit and sold or used as an independent product, can be stored in a readable storage medium. Based on such understanding, the technical scheme of the embodiment of the present application essentially or the part that contributes to the prior art or the whole or part of the technical scheme can be embodied in the form of a software product, which is stored in a storage medium and includes a plurality of instructions for causing an apparatus (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the method described in the embodiments of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various storage medium that can store program codes.

[0281] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any change or replacement within the technical scope disclosed by the present application should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. An application keep-alive method, characterized by, The method is applied to an electronic device including a first mode and a second mode, and the method comprises: In the first mode, a first multitask management interface is displayed, the first multitask management interface including a first card corresponding to a first application and a second card corresponding to a second application; In response to a locking operation on the first application, a second multitask management interface is displayed, the second multitask management interface including the first card and the second card and a locking identifier corresponding to the first application; After receiving a user's empty recent task operation on the second multitask management interface, the second card is removed from the second multitask management interface; In response to a user's first operation, a desktop interface of the second mode is displayed; In response to a user's second operation, a third multitask management interface is displayed, the third multitask management interface including a third card corresponding to the first application; After receiving a user's empty recent task operation on the third multitask management interface, the third card is removed from the third multitask management interface; In response to a user's third operation, a desktop interface of the first mode is displayed; In response to a user's fourth operation, a fourth multitask management interface is displayed, the fourth multitask management interface not including a card of the first application.

2. The method of claim 1, wherein, The method further comprises: In the first mode, a fifth multitask management interface is displayed, the fifth multitask management interface including a fourth card corresponding to a first application and a fifth card corresponding to a second application; In response to a locking operation on the first application, a sixth multitask management interface is displayed, the sixth multitask management interface including the fourth card and the fifth card and a locking identifier corresponding to the first application; After receiving a user's empty recent task operation on the sixth multitask management interface, the fifth card is removed from the sixth multitask management interface; In response to a user's fifth operation, a desktop interface of the second mode is displayed; In response to a user's sixth operation, a seventh multitask management interface is displayed, the seventh multitask management interface including a sixth card corresponding to the first application; In response to a user's seventh operation, a desktop interface of the first mode is displayed; In response to a user's eighth operation, an eighth multitask management interface is displayed, the eighth multitask management interface including a seventh card of the first application and a locking identifier 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 multitask management interface is displayed, the ninth multitask management interface including an eighth card corresponding to a first application and a ninth card corresponding to a second application; In response to a locking operation on the first application, a tenth multitask management interface is displayed, the tenth multitask management interface including the eighth card and the ninth card and a locking identifier corresponding to the first application; After receiving a user's empty recent task operation on the tenth multitask management interface, the ninth card is removed from the tenth multitask management interface; In response to a user's ninth operation, a desktop interface of the second mode is displayed; In response to a tenth operation of the user, a eleventh multitask management interface is displayed, the eleventh multitask management interface including a tenth card corresponding to the first application; In the second mode, the electronic device is restarted; After the electronic device is restarted, a desktop interface of the first mode is displayed; In response to an eleventh operation of the user, a twelfth multitask management interface is displayed, the twelfth multitask management interface including an eleventh card corresponding to the first application and a locked identifier corresponding to the first application.

4. The method according to claim 1 or 2, characterized in that, The method further includes: In the second mode, in response to a twelfth operation of the user, a first interface is displayed, the first interface including a plurality of application floating windows; In response to a thirteenth operation of the user, a thirteenth multitask management interface is displayed, the thirteenth multitask management interface including a twelfth card, the twelfth card including thumbnails of the plurality of application floating windows.

5. The method according to claim 1 or 2, characterized in that, The method further includes: In the second mode, a second interface is displayed, a bottom task bar of the second interface including a first application icon; In response to an operation of the user dragging the first application icon to a first position on the display screen and releasing, a floating window of an application indicated by the first application icon is displayed at the first position.

6. The method of claim 1 or 2, wherein, The method further includes: In the second mode, a third interface is displayed, the third interface including a first icon; After receiving an operation of the user selecting the first icon, a plurality of applications are started; floating windows of the plurality of applications are displayed according to a layout indicated by the first icon.

7. The method according to claim 1 or 2, characterized in that, The method further includes: In the second mode, a fourth interface is displayed, the fourth interface including floating windows of a plurality of applications displayed according to a first layout, the fourth interface further including a second icon, the second icon indicating a second layout; After receiving an operation of the user selecting the second icon, the floating windows of the plurality of applications are displayed according to the second layout.

8. An electronic device, comprising: An electronic device includes a memory, a processor, and a display screen; the display screen is configured to display a user interface, the memory is coupled to the processor, the memory is configured to store computer program code, the computer program code includes computer instructions, and the processor invokes the computer instructions to cause the electronic device to perform the method of any one of claims 1-7.

9. A computer readable storage medium having stored thereon computer instructions, wherein, The computer instructions, when executed by the processor, implement the method of any one of claims 1-7.

10. A computer program product comprising computer instructions, characterized in that, The computer instructions, when executed by the processor, implement the method of any one of claims 1-7.

Images